NetBSD Packages Collection Releases A New Branch

jschauma writes "On behalf of the pkgsrc team, Alistair Crooks announced today that a new pkgsrc-2004Q1 branch of the NetBSD Packages Collection was created last night, and the freeze on committing to the pkgsrc trunk is now over. This branch, which includes some 4518 actively-maintained and supported packages, introduces a self-hosted pkgsrc infrstructure as part of the ever growing support of even more operating systems as well as a number of other goodies. Please see Alistair's message to the netbsd-announce mailing list for details."

Re:tired of bsd trolls :-(

[HitScan]

Slashdot has to post BSD stories once in a while so they can act like a sponge for the retards to ruin and keep them from ruining all the other stories. The comments are useless on any BSD story, due to retard concentration. Allowing Anonymous posts doesn't help anything.

Packages

[Anonymous Coward]

There are a few important points about any package management system that should be fulfilled.

1. Packages should have all of their files independent from each other. Administering this type of system is far easier, as there's never any question where a file comes from.
2. There is never any reason to recompile a package. Symlinks should enable all packages to have their dynamically linked libraries upgradeable without recompiling that package.
3. There is never any reason to remove a package. Since the files are kept seperate, versioning problems don't exist. If nobody is using a version of a package, it can be removed. Otherwise there's no reason to bother.

Re:Packages

[endx7]

Your list is somewhat dependant on whoever wrote the original software. Ports/pkgsrc/etc are pretty much at the mercy of whoever wrote the software in the first place.