Why aren't all files in a Package?
Certain core files that come with freebsd don't seem to belong to any package, one of them being zlib. I was trying to figure out what version of zlib FreeBSD is using, but since it wasn't part of any package, it was a little difficult, I had to edit libz.so and greped for 1.1.4. Since I found that, I'm assuming that that's the correct version, but I think a simple pkg_info -W should have answered that. Also, programs like named seem to come default as part of named and therefore have no package associated with them, but there is also a version in the ports collection. How do I uninstall the version in /usr so I can be assured that the version being invoked is in /usr/local. The last problem is that it makes it more difficult to find the source code for a particular core program. Is there any way I can access it any easier like I was doing in debian? dpkg -S /path/to/file tells me the package name, then apt-get source package downloads that package. -- I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C pgp0.pgp Description: PGP signature
Re: Why aren't all files in a Package?
On Sun, Feb 08, 2004 at 07:00:50AM -0800, Loren M. Lang wrote: Certain core files that come with freebsd don't seem to belong to any package, one of them being zlib. I was trying to figure out what version of zlib FreeBSD is using, but since it wasn't part of any package, it was a little difficult, I had to edit libz.so and greped for 1.1.4. Since I found that, I'm assuming that that's the correct version, but I think a simple pkg_info -W should have answered that. The base system isn't distributed as packages. This is mostly for historical reasons, although it's not straightforward to make the change. Kris pgp0.pgp Description: PGP signature
