Hello, On Monday 06 October 2008 07:23:37 Eygene Ryabinkin wrote:
> But downloading the INDEX file from the central server seemed to be the > best way, since it almost always gives one the latest port versions, so > I had implemented this in a first place. I've been following this, but I don't agree that (port|pkg_)audit should do this, from the very perspective you're writing this program from: On Sunday 28 September 2008 11:49:18 Eygene Ryabinkin wrote: > 4. I feel that it is Unix-way to do the things: create small utilities > that do their (small) job in a proper fashion. Instead, it can provide installed-pkgname<seperator>pkgorigin output. Then, any utility can check whether a new version is available, using what ever source it finds relevant. For example, it is completely irrelevant if a new version is available on the FreeBSD servers, when your machine uses a buildserver in a local network. For those machines it's relevant whether their build server has a new version and one can automatically upgrade if one so desires. Similarly, if your /usr/ports is ahead of the FreeBSD's INDEX.bz2, you're again reporting false information. It's also quite trivial to provide this availibility information in a daily security script, for the "majority of cases" and it's better to have tunables like _use_remote_portindex, _use_portsdir=/bigdisk/usr/ports in a script. -- Mel _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"