Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 1 May 2000 22:17:03 +0200
From:      Neil Blakey-Milner <nbm@mithrandr.moria.org>
To:        David Heller <dheller1@rochester.rr.com>
Cc:        ports@FreeBSD.org
Subject:   Re: stop complaining about x11 please (was: Re: Why does PORTS SUCK so BADLY!?)
Message-ID:  <20000501221703.A73550@mithrandr.moria.org>
In-Reply-To: <390DDE5F.69E94C2C@rochester.rr.com>; from dheller1@rochester.rr.com on Mon, May 01, 2000 at 03:43:27PM -0400
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>

next in thread | previous in thread | raw e-mail | index | archive | help
[ questions -> ports ]

> > > With my qt145/kdelibs11 maintainer hat on, I'd just like to point out that
> > > GL is used in Qt for the QtGL extensions. However, it does seem that most
> > > programs don't use GL, so perhaps you could conjure a patch to the Qt port
> > > to allow command-line disabling of GL.
> > 
> > My benchmark would be that if the original tarball configures and
> > builds without this dependency, the port should not insist on it
> > (there should be some user-choice); but if the original configure
> > script refuses to continue, then the dependency should be retrieved
> > and built automatically.  To take another example, mpeg-lib or aalib
> > in Gimp are optional, but gtk/glib are not.  Either there could be a
> > PORT_MINIMAL=yes or the user could be prompted with a (y/n) dialogue
> > whether such optional packages should be retrieved, or there could
> > just be warning messages about missing functionality.  I don't know
> > how difficult it would be to implement but I feel it would be useful.
> 
> It would be nice when installing ports that, the user be given some
> choices if there are different options avail. It would avoid having to
> interrupt the build process and re-making.

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

Neil
-- 
Neil Blakey-Milner
Hacker In Chief, Sunesi Clinical Systems
nbm@mithrandr.moria.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




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