Date: Tue, 2 May 2000 07:56:26 -0400 From: Will Andrews <andrews@technologist.com> To: Neil Blakey-Milner <nbm@mithrandr.moria.org> Cc: David Heller <dheller1@rochester.rr.com>, ports@FreeBSD.ORG Subject: Re: stop complaining about x11 please (was: Re: Why does PORTS SUCK so BADLY!?) Message-ID: <20000502075626.D392@argon.blackdawn.com> In-Reply-To: <20000501221703.A73550@mithrandr.moria.org>; from nbm@mithrandr.moria.org on Mon, May 01, 2000 at 10:17:03PM %2B0200 References: <009b01bfb389$96546cf0$b8209fc0@marlowe> <20000501101044.F24573@fw.wintelcom.net> <00b901bfb38f$e4625cd0$b8209fc0@marlowe> <20000501105116.B32172@ccsales.com> <20000501113038.I24573@fw.wintelcom.net> <20000501234432.A2998@physics.iisc.ernet.in> <20000501150045.A391@argon.blackdawn.com> <20000502004233.A3681@physics.iisc.ernet.in> <390DDE5F.69E94C2C@rochester.rr.com> <20000501221703.A73550@mithrandr.moria.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 01, 2000 at 10:17:03PM +0200, Neil Blakey-Milner wrote: > Something like portconf: http://people.FreeBSD.org/~nbm/portconf/ ? > > portconf is a mechanism to provide a tool with information about what > options a port understands. It's based on the apache13-php3 build, and > could theoretically be used in friendly ports installers, like the > gtk/ncurses front-ended one I wrote to accompany portconf. > > portconf comes with a perl version to live in ports-base so no extra > software is needed, and a c/ncurses and a c/gtk version for other uses. > > It's almost the exact opposite of debconf in debian, which configures > the package during/after install, whereas portconf configure the build. > > It should work well together with WITH_*. How can we implement portconf in the least intrusive possible method ? I'm thinking of having a files/options file that is included by bsd.port.mk to generate a set of defines that can be used by the user to add in options at build time. Portconf can then parse said file to generate the list of options. How this will be done is another story. But if done well, I think it will make a great substitute (i.e. easy to do) for the current -DWITH[OUT,]_X hack that's in some port Makefiles. I don't think portconf belongs in ports-base, however... I think the default method should be to use bsd.port.mk to parse files/options and generate a dialog(1) script based on it. Maybe you could explain why doing configuration without X installed with your ncurses version would be better. But if we're going to use an XML file, why not just rewrite the whole damn ports tree in XML? It seems like a waste to put XML files in the tree just for portconf. Which is why I'm suggesting files/options here. (Because it can be used by more than just portconf, at least theoretically). Respectfully, -- Will Andrews <andrews@technologist.com> GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000502075626.D392>