Date: Sat, 7 Jan 2006 19:55:28 +1100 From: Sam Lawrance <boris@brooknet.com.au> To: Doug Barton <dougb@freebsd.org> Cc: Jeremy Messenger <mezz7@cox.net>, freebsd ports <freebsd-ports@freebsd.org> Subject: Re: New /bin/sh based script to manage ports Message-ID: <D70EBFDD-B18B-43CC-A29F-1937DEA5322E@brooknet.com.au> In-Reply-To: <43BF7F8D.6080809@FreeBSD.org> References: <43BCF31F.8050900@FreeBSD.org> <op.s2w24xlg9aq2h7@mezz.mezzweb.com> <43BF7F8D.6080809@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/01/2006, at 7:45 PM, Doug Barton wrote: > 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. I thought about this the other day... it turns out you can 'make -V SOMEVAR' whether there is a Makefile or not.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D70EBFDD-B18B-43CC-A29F-1937DEA5322E>