HEADS UP: pkg-plist strict enforcement starting
lupe at lupe-christoph.de
Fri Jan 14 04:06:43 PST 2005
Quoting Kirill Ponomarew <krion at voodoo.oberon.net>:
> 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? Put them in /root/.foo.conf rather than
| lupe at lupe-christoph.de | http://www.lupe-christoph.de/ |
| "... putting a mail server on the Internet without filtering is like |
| covering yourself with barbecue sauce and breaking into the Charity |
| Home for Badgers with Rabies. Michael Lucas |
More information about the freebsd-ports