Date: 20 Jun 2003 06:38:47 -0400 From: "Brandon S. Allbery " KF8NH <allbery@ece.cmu.edu> To: Joe Marcus Clarke <marcus@marcuscom.com> Cc: ports@freebsd.org Subject: Re: FreeBSD Port: mozilla-devel-1.4b Message-ID: <1056105527.2609.8.camel@rushlight.kf8nh.apk.net> In-Reply-To: <1055953667.314.13.camel@gyros> References: <46462.63.104.35.130.1055950651.squirrel@email.polands.org> <1055950865.83103.32.camel@rushlight.kf8nh.apk.net> <1055953667.314.13.camel@gyros>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2003-06-18 at 12:27, Joe Marcus Clarke wrote: > > I find it useful to go through the ports Makefiles on occasion and find > > the current WITH_*/WITHOUT_* flags. (It would be nice if there were an > > easy way to do this; mostly I end up scanning for them after a > > "portupgrade -a" and then go through and rebuild ports.) > > I print all the tunable options during pre-everything, so you should see > a list on your screen when you try to build mozilla. And that's what I look for when I scan the portupgrade log file. Which still leaves that (a) I have to do the portupgrade first and (b) not every port with tunables prints them. What would be nice would be a standard make target which listed the tunables for a port; I could then run "portupgrade -a" forcing that target to see the tunables (which often seem to change on me) and adjust my pkgtools.conf before building everything. -- brandon s allbery [openafs/solaris/japh/freebsd] allbery@kf8nh.apk.net system administrator [linux/heimdal/too many hats] allbery@ece.cmu.edu electrical and computer engineering KF8NH carnegie mellon university [better check the oblivious first -ke6sls]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1056105527.2609.8.camel>