On Sat, Dec 13, 2008 at 10:10:26AM +0100, Landry Breuil wrote:
> On Fri, Dec 12, 2008 at 11:27:44PM -0600, Marco Peereboom wrote:
> > Ted is right. I do know about -M but I use it so frequently that I
> > always have to find it in the man. pkg_info could should be able to
> > display this info like pkg_info cups. That makes intuitive sense to me
> > and I think others as well.
>
> pkg_info displays package _information_, which is terse. pkg_info -M
> displays additional information about how to use the given package, only
> if it's needed,
there are 300 MESSAGE files in ports ...
> and it can be sometimes big
I think some is outright bloat. take the cups MESSAGE for example:
>>>
To enable CUPS, execute '${PREFIX}/sbin/cups-enable' as root.
To disable CUPS, execute '${PREFIX}/sbin/cups-disable' as root.
To start cups at boot time, add the following to
/etc/rc.local:
if [ -x ${PREFIX}/sbin/cupsd ]; then
echo -n ' cupsd'; ${PREFIX}/sbin/cupsd
fi
Starting cupsd will overwrite /etc/printcap. A backup copy of this file
is saved as /etc/printcap.pre-cups by '${PREFIX}/sbin/cups-enable'
and will be restored when you run '${PREFIX}/sbin/cups-disable'.
<<<
is it really necessary to have an example for rc.local? isn't it going
to be more-or-less the same for all daemons? sometimes there are
exceptions, but shouldn't this stuff be covered in manuals? is all
the info in these MESSAGE files really needed?
couldn't the CUPS message be shortened to something like:
Starting cupsd will overwrite /etc/printcap. CUPS has "replacement"
programs for some system programs. ${PREFIX}/sbin/cups-enable
can be used to backup the current printcap and system programs.
${PREFIX}/sbin/cups-enable can be used to restore them.
> (and when too big, separated
how is "too big" defined? is the above abbreviated CUPS message too
big to add to the default pkg_info output?
> in a given README.OpenBSD, which pkg_info -M points to).
how about a standard directory for README.OpenBSD files?
${PREFIX}/share/README.OpenBSD/port-x.y ? and then move the majority
of this stuff there? I think this would make such files much easier
to find.
of course, I'm responsible for some of these MESSAGE files. I really
do see the "noise" during install/upgrade as a problem, as people
(including myself) probably don't always read it, even though
ignoring it can lead to problems ...
--
[email protected]
SDF Public Access UNIX System - http://sdf.lonestar.org
