Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 07 Jan 2006 11:55:22 -0600
From:      "Jeremy Messenger" <mezz7@cox.net>
To:        "Doug Barton" <dougb@freebsd.org>
Cc:        freebsd ports <freebsd-ports@freebsd.org>
Subject:   Re: New /bin/sh based script to manage ports
Message-ID:  <op.s20r2kny9aq2h7@mezz.mezzweb.com>
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 Sat, 07 Jan 2006 02:45:01 -0600, Doug Barton <dougb@FreeBSD.org> 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.

Np, right now I am trying to brainstorm on old distfiles issue to see if I  
can think of.

>> 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.

Here too, but mine is ports.conf. ;-) Looks like KOMATSU Shinichiro  
<koma2@lovepeers.org> has the best solution.

Cheers,
Mezz

> 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


-- 
mezz7@cox.net  -  mezz@FreeBSD.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/  -  gnome@FreeBSD.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.s20r2kny9aq2h7>