From owner-freebsd-ports@FreeBSD.ORG Sat Jan 7 08:45:06 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A321B16A41F for ; Sat, 7 Jan 2006 08:45:06 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mail2.fluidhosting.com [204.14.90.12]) by mx1.FreeBSD.org (Postfix) with SMTP id 2160643D45 for ; Sat, 7 Jan 2006 08:45:06 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 62765 invoked by uid 399); 7 Jan 2006 08:45:05 -0000 Received: from localhost (HELO ?192.168.1.100?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 7 Jan 2006 08:45:05 -0000 Message-ID: <43BF7F8D.6080809@FreeBSD.org> Date: Sat, 07 Jan 2006 00:45:01 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5 (X11/20051226) MIME-Version: 1.0 To: Jeremy Messenger References: <43BCF31F.8050900@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd ports Subject: Re: New /bin/sh based script to manage ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jan 2006 08:45:06 -0000 Jeremy Messenger wrote: > I haven't play with your script yet, but I only read it so far. Thanks for taking a look, and for your feedback. > I think > you should get your script to be able to read in the make.conf (by > include) for PKG_DBDIR, PORTSDIR, DISTDIR and etc in case if someone > tweak it. I think it's more friendly with ports that way. This is a reasonable request, and I should point out that the script does handle DISTDIR properly now. However, the other two present a chicken and egg problem if I choose to use 'make -V' to get the values of these variables (where do I cd to?). There is an alternative, which is to use code similar to what I wrote for the current version of /etc/rc.d/devfs to parse /etc/make.conf manually, but even that is subject to error. For example, I separate my base stuff into /etc/make.conf and ports to /etc/make-ports.conf. If there is a lot of call for this, I could add command line options (that could subsequently be read from a portmaster.rc file) although I'm sensitive to the issue that users who relocate these directories already have a lot of places to set those options. OTOH, I put my ports tree in a different directory than /usr/ports, but I learned long ago that the easiest way to handle that is to create a symlink to it in /usr. YMMV of course. I've uploaded a new version that fixes a typo that was reported here, and removes references to the name I used for the script during development. http://dougbarton.us/portmaster.html if anyone is still interested. Thanks to all those who've provided feedback so far. Doug -- This .signature sanitized for your protection