ports/128646: ports-mgmt/portmaster [feature request]: naming log files, hooks

clemens fischer ino-news at spotteswoode.dnsalias.org
Thu Nov 6 12:20:01 UTC 2008

>Number:         128646
>Category:       ports
>Synopsis:       ports-mgmt/portmaster [feature request]: naming log files, hooks
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Thu Nov 06 12:20:00 UTC 2008
>Originator:     clemens fischer
>Release:        FreeBSD 8.0-CURRENT i386
System: FreeBSD spotteswoode.dnsalias.org 8.0-CURRENT FreeBSD 8.0-CURRENT #5 r184224M: Fri Oct 24 19:31:25 CEST 2008 root at spotteswoode.dnsalias.org:/usr/local/obj/usr/src-main/sys/spott_fbsd8_i386 i386


Portmaster(8) may well be the best thought-out port management tool, but
for my usage pattern a small nit remains:  there's no provision to name
log files.  I always want a complete log to be able to provide it to
maintainers in case of trouble or as a note to myself.

If there was an option 'N' taking an argument providing a template for
the name of a log file created _always_, and if the template could use
variables set by portmaster like ${PORT_CATEGORY} and ${PORT_NAME}, the
template could be eval'ed for every port and result in the name of
a log file.  I currently fake this functionality using a wrapper script,
but as portmaster doesn't provide hooks, the wrapper is imperfect.

Hooks would be a more general alternative.  To me, naming log files is
the only feature missing, but other people might have different needs.
They might want to set options differently depending on port category
and name.  Portmaster already sets and uses a number of useful
variables, it might as well test for the availability and make use of
user supplied code snippets, like etc/dhclient-(enter|exit)-hooks for
the dhclient script.  They should be wrapped in "set -x" and "set +x"
though, so their output gets included in the output.



regards, clemens

More information about the freebsd-ports-bugs mailing list