NetBSD Branches pkgsrc-2005Q1

jschauma writes "NetBSD's Alistair Crooks has announced the availability of the new stable branch pkgsrc-2005Q1 of the NetBSD Packages Collection (aka pkgsrc). This branch includes all the updates to the thousands of existing and additions of hundreds of new applications since the hereby obsoleted pkgsrc-2004Q4 branch. Some noteworthy infrastructure changes applicable to all 13 operating systems for which pkgsrc is available include the support for multiple digests to check the integrity of the distribution files as found on the Internet (triggered by the recently-found problems with the SHA-1 algorithm) and the so-called alternates framework."

Wired News Confirms *BSD is Dying

[Anonymous Coward]

IT IS OFFICIAL; WIRED NEWS CONFIRMS: LINUX IS SUPERIOR TO *BSD
*BSD is Dying, Says Respected Journal

Linux advocates have long insisted that open-source development results in better and more secure software. Now they have statistics to back up their claims.

According to a four-year analysis of the 5.7 million lines of Linux source code conducted by five Stanford University computer science researchers, the Linux kernel programming code is better and more secure than the programming code of *BSD.

The report,

Binary packages?

[Anonymous Coward]

Where are the binary packages for pkgsrc-2005Q1? I can't find them on ftp.netbsd.org.

Re:Binary packages?

[jschauma]

Binary packages will be uploaded as soon as the various bulk-builds on the different operating systems and NetBSD ports have completed. This takes a while on some older platforms, though I'd expect some of the faster platforms to soon upload.

Re:Binary packages?

[Anonymous Coward]

I was the original AC who asked about where the pkgsrc-2005Q1 binary packages are.

I've heard a lot of good things about pkgsrc, and how it's ultra-portable etc. That's why I'm surprised that pkgsrc still does not have a decent way to do something as "simple" as upgrading binary packages recursively. I say "simple" since upgrading binary packages should be relatively straightforward, seeing that pkgsrc developers must have looked into a lot of complex package management issues (after all, pkgsrc is portabl

Re:Binary packages?

[jschauma]

From what I read here, I understand that 'pkg_add -r' automatically updates the given package and all of its dependencies. It's not quite clear to me, though, what exactly that means. After upgrading a given package, does it: (a) upgrade each package that depends on this one to the latest available binary package? (b) upgrade only those packages that rely on the newer version (for example, for ABI changes) but leave others (the ones that will work perfectly fine with the older version as well as the newer

Re:Binary packages?

[Anonymous Coward]

Original where-are-binary-packages AC again.

Thanks for your insight into pkgsrc.

This is what the OpenBSD man page says about pkg_add -r.

-r Allow replacing existing packages. The code will try to take
every precaution to make sure the update can proceed before re-
moving the old package and adding the new one, and it should al-
so handle shared libraries correctly.

I guess it's unfair to compare NetBSD's pkgsrc to OpenBSD's package management. I think that's because NetBSD's pkgsr

Re:Binary packages?

[Anonymous Coward]

The answer to the question to recursively upgrade binary packages seems to be not pkg_chk, but pkg_add -uu. From its manpage:

-u If the package that's being installed is already installed,
either in the same or a different version, an update is per-
formed. If this is specified twice, then any dependant packages
that are too old will also be updated to fulfill the dependency.
See below for a more detailed description of the process.

Re:Binary packages?

[jschauma]

Binary packages have been uploaded (so far) for:
NetBSD-2.0/amd64 [netbsd.org], NetBSD-2.0/i386 [netbsd.org], NetBSD-1.6.2/i386 [netbsd.org], NetBSD-2.0/sparc [netbsd.org] and IRIX64-6.5 [netbsd.org] (including PGP signed checksum files).

Re:yeah !!

[setagllib]

Would Linux 2.6 be where it is if it had been conservatively developed on from 2.4? Short answer: No. Long answer: Definitely not.

Branching lets people use a continuing product with one development model while another version of the same product is worked on with another development model. After a certain agreed-upon stage of development, the roles change. For instance, the unstable branch gets to a stage of maturity, and it is made the stable branch.

That's why BSDs always have something stable and typi