HEADS UP: pkg-plist strict enforcement starting

Kirill Ponomarew krion at voodoo.oberon.net
Fri Jan 14 05:29:59 PST 2005


On Fri, Jan 14, 2005 at 01:06:38PM +0100, Lupe Christoph wrote:
> > You can try cmp(1) in pkg-plist to compare configurations files.
> > Take a look at ports collection, there are enough examples.
> 
> Not useful for munin-node because it creates system-dependent
> symlinks. I'm not aware of any other port doing this. And munin-main
> will create a lot of files if a cron run happens to coincide with
> the few moments the port is installed during the test.
> 
> I have only the option to burden the user with doing all the parts
> of the installation that create state that cannot be easily undone
> or are detrimental to the test like the crontab entry. Things that
> are easily done automatically.
> 
> Also I wonder if having a default of "No" for the rc.conf variable
> (i.e. 'don't run the daemon') is really necessary. Is this required?
> The whole point of installing munin-node is to run the daemon.
>  
> > It's better to use ~/.your_port directory in such cases.
> 
> For system-wide defaults?

For files which should be changed/deleted/added etc while software is
running.

-Kirill
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20050114/b1be633a/attachment.bin


More information about the freebsd-ports mailing list