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:
---------------------------------
WRKDIRPREFIX=/usr/obj
.if ${.CURDIR:M*/devel/gmake}
WITHOUT_NLS=yes
.endif
.if ${.CURDIR:M*/mail/fetchmail}
.MAKEFLAGS: -DWITH_NTLM
.endif
.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
---------------------------------
Note specifically the ".MAKEFLAGS" trick above that IMHO won't easily
work with portconf.
Helge
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
