HEADS UP: pkg-plist strict enforcement starting
krion at voodoo.oberon.net
Fri Jan 14 03:29:45 PST 2005
On Fri, Jan 14, 2005 at 01:04:04PM +0200, Adi Pircalabu wrote:
> > I'm going to be careful about not allowing the "questionable" packages
> > to fall foul of the pkg-plist checking, until we decide one way or the
> > other whether they should be considered "broken".
> This is a tricky situation from my point of view. I'm following this
> thread with a lot of interest since I'll be managing a port which CAN
> NOT honor pkg-plist strict checking. Here are few details:
> - The configuration files are created and heavily modified at install
> time from .dist files, will be modified as needed and should not be
> deleted at uninstall - the configuration should be kept for a later
> upgrade. This will definitely break "make install deinstall" on the
> packages cluster, but the files are required since they must contain
> information about various modules and plugins of the port, and this
> information must be written through a daemon started at post-install.
You can try cmp(1) in pkg-plist to compare configurations files.
Take a look at ports collection, there are enough examples.
> - The port uses several other files (plugins, modules) which will be
> updated from time to time. Also, new modules / plugins whose names could
> not be initially listed in pkg-plist may be added, as well as existing
> ones may be updated or even deleted.
It's better to use ~/.your_port directory in such cases.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20050114/b2f1ff1a/attachment.bin
More information about the freebsd-ports