Date: Wed, 23 Aug 2006 09:39:47 -0500 From: "Scot Hetzel" <swhetzel@gmail.com> To: "Helge Oldach" <helge.oldach@atosorigin.com> Cc: ports@freebsd.org, mwlucas@blackhelicopters.org Subject: Re: "the best" port update tool Message-ID: <790a9fff0608230739v36143292k68852b1677f1d7f4@mail.gmail.com> In-Reply-To: <200608231350.PAA24812@galaxy.hbg.de.ao-srv.com> References: <790a9fff0608220532h790dd310jd15d9c6cfb990b11@mail.gmail.com> <200608231350.PAA24812@galaxy.hbg.de.ao-srv.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/23/06, Helge Oldach <helge.oldach@atosorigin.com> wrote:
> Scot Hetzel:
> >While the portmanager, portupgrade, and portmaster tools allow you to
> >keep your specific port options in a file, they are incompatible with
> >each other and when building directly from /usr/ports, as the port
> >options in these seperate files are not available to the other tools
> >or to /usr/ports. This deficiency has been fixed with the
> >sysutils/portconf port, where you can specify your port options in
> >PREFIX/etc/ports.conf file, and these tools and direct building from
> >/usr/ports will use these port options.
>
> Hmm... What is wrong with directly amending /etc/make.conf with, for
> example:
>
Nothing wrong with doing it this way, just that a newbie has to find
this syntax, and edit their make.conf accordingly. Where with a
newbie using the ports.conf file, they just add each option on one
line, and let the magic added by the sysutils/portconf to
/etc/make.conf do all the work for them.
An additional benifit is that you don't clutter your make.conf file
with all of these .if ... .endif statements when you have more than 10
ports that you set with custom options.
> ---------------------------------
> WRKDIRPREFIX=/usr/obj
>
> .if ${.CURDIR:M*/devel/gmake}
> WITHOUT_NLS=yes
> .endif
>
> .if ${.CURDIR:M*/mail/fetchmail}
> .MAKEFLAGS: -DWITH_NTLM
> .endif
>
:
> Note specifically the ".MAKEFLAGS" trick above that IMHO won't easily
> work with portconf.
>
That will work with portconf, without using .MAKEFLAGS:
devel/gmake: WITHOUT_NLS
mail/fetchmail: WITH_NTLM
You could have also used "WITH_NTLM=YES" instead of .MAKEFLAGS in your
make.conf and the fetchmail port would be built with NTLM support.
> .if ${.CURDIR:M*/sysutils/uptimed}
> post-install-script:
> -${RM} ${PREFIX}/www/cgi-bin/uprecords.conf
> -${RM} ${PREFIX}/www/cgi-bin/uprecords.cgi
> -${RM} ${PREFIX}/www/cgi-bin/uprecords.header
> -${RM} ${PREFIX}/www/cgi-bin/uprecords.footer
> -${RMDIR} ${PREFIX}/www/cgi-bin
> -${RMDIR} ${PREFIX}/www
> .endif
> ---------------------------------
>
This portconf can't do.
Scot
--
DISCLAIMER:
No electrons were mamed while sending this message. Only slightly bruised.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?790a9fff0608230739v36143292k68852b1677f1d7f4>