On Mon, 1 Dec 2003, Perry E.Metzger wrote: > party". Our pkgsrc infrastructure exists to make it easy to compile > third party software, but we do not claim that Emacs and /bin/ls are > supported the same way. > > We've got about 4500 packages in pkgsrc -- a fraction of the number > some folks like Debian support, but quite a number -- and in the
Counting packages doesn't work well. Debian splits up many, many software suites into separate packages, such as docs, libraries, programs/ executables, development headers, and shared data. It is common to have one package in pkgsrc be represented by three-or-more Debian packages. Only for a few packages in pkgsrc are they split up. (I do agree that separating big software into seperate packages is a good idea -- I use new freedesktop.org xlibs which is in over 15 packages.) > course of making them all work we routinely find that we have to fix > things in NetBSD. For example, programs like xmms have inspired many > changes to our threads system. Another thing that is interesting is that most of pkgsrc is usable on non-NetBSD systems. Many admins use it to have a consistent third-party software installation method under Solaris and Linux. pkgsrc is used (or has been used) under BSD/OS, Mac OS X, Darwin OS, Irix, FreeBSD, OpenBSD, HP-UX, and others. In fact, one pkgsrc developer is beginning to use pkgsrc (via mingw compiler) to provide software for Windows platforms. I even use pkgsrc to build and install Linux the kernel, glibc, iptables, vixie-cron, shadow, all components of my Linux distribution. (A few of these pkgsrc packages are not in pkgsrc or pkgsrc-wip yet though.) Jeremy C. Reed echo '9,J8HD,[EMAIL PROTECTED]:[EMAIL PROTECTED];[EMAIL PROTECTED]@5GBIELD54DL>@8L?:5GDEJ8LDG1' |\ sed ss,s50EBsg | tr 0-M 'p.wBt SgiIlxmLhan:o,erDsduv/cyP'
