From owner-freebsd-ports-bugs@FreeBSD.ORG Thu Nov 6 12:20:01 2008 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 363E31065674 for ; Thu, 6 Nov 2008 12:20:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 105708FC2B for ; Thu, 6 Nov 2008 12:20:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mA6CK05g010280 for ; Thu, 6 Nov 2008 12:20:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mA6CK0wO010279; Thu, 6 Nov 2008 12:20:00 GMT (envelope-from gnats) Resent-Date: Thu, 6 Nov 2008 12:20:00 GMT Resent-Message-Id: <200811061220.mA6CK0wO010279@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-ports-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, clemens fischer Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E46CE1065670 for ; Thu, 6 Nov 2008 12:10:45 +0000 (UTC) (envelope-from ino-news@kabelmail.de) Received: from smtpa.mediabeam.com (smtpa1.mediabeam.com [194.25.41.13]) by mx1.freebsd.org (Postfix) with ESMTP id 6E6128FC1C for ; Thu, 6 Nov 2008 12:10:44 +0000 (UTC) (envelope-from ino-news@kabelmail.de) Received: from spotteswoode.dnsalias.org (91-64-171-198-dynip.superkabel.de [91.64.171.198]) (authenticated bits=0) by smtpa.mediabeam.com (8.13.1/8.13.1) with ESMTP id mA6CBXcs015853 for ; Thu, 6 Nov 2008 13:11:34 +0100 Received: by spotteswoode.dnsalias.org (Postfix, from userid 0) id 9813A7A068; Thu, 6 Nov 2008 13:10:37 +0100 (CET) Message-Id: <20081106121037.9813A7A068@spotteswoode.dnsalias.org> Date: Thu, 6 Nov 2008 13:10:37 +0100 (CET) From: clemens fischer To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Cc: clemens fischer Subject: ports/128646: ports-mgmt/portmaster [feature request]: naming log files, hooks X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Nov 2008 12:20:01 -0000 >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 >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Thu Nov 06 12:20:00 UTC 2008 >Closed-Date: >Last-Modified: >Originator: clemens fischer >Release: FreeBSD 8.0-CURRENT i386 >Organization: >Environment: System: FreeBSD spotteswoode.dnsalias.org 8.0-CURRENT FreeBSD 8.0-CURRENT #5 r184224M: Fri Oct 24 19:31:25 CEST 2008 root@spotteswoode.dnsalias.org:/usr/local/obj/usr/src-main/sys/spott_fbsd8_i386 i386 >Description: 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. >How-To-Repeat: >Fix: regards, clemens >Release-Note: >Audit-Trail: >Unformatted: