Date: Sun, 21 Jul 2002 00:22:50 +0100 From: Nik Clayton <nik@FreeBSD.ORG> To: "Simon 'corecode' Schubert" <corecode@corecode.ath.cx>, Nik Clayton <nik@FreeBSD.ORG>, ports@FreeBSD.ORG Subject: Re: Proposed new 'options' target Message-ID: <20020720232250.GE37802@clan.nothing-going-on.org> In-Reply-To: <20020720175640.GI52296@squall.waterspout.com> References: <20020720162928.GD37802@clan.nothing-going-on.org> <20020720190909.458442de.corecode@corecode.ath.cx> <20020720175640.GI52296@squall.waterspout.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--cpvLTH7QU4gwfq3S Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jul 20, 2002 at 12:56:40PM -0500, Will Andrews wrote: > Nik, I looked at your patch. I think (but would have to ask > gnome@) that WITH_GNOME check should go in bsd.gnomeng.mk. =20 Makes sense. All the sample WITH_* stuff is up in the air, and should be put in to whichever file makes more sense. > And > as Simon says, the interface should be flexible, allowing people > to choose from dialog, gui, or perhaps cli, what you implemented. No problem with that. However, can we least agree on a minimal set of features this must have, and the API that porters should use in order to take advantage of these? Introducing GUIs in to the mix is going to make things more complicated. For example, with the pure_ftpd example, the WITH_LANG stuff isn't a=20 simple binary option, it's a list of valid values, which are going to need to be enumerated in some fashion (along with information about which widget should be used to display them, any input checking constraints that apply, whether or not any options are mutually exclusive, and so=20 forth). That's a huge can of worms. We're essentially talking about a new configuration file for each port=20 that has options, that explains in some detail what those options are,=20 how they should be presented to the end user, and so on. I suggest that the history of the project shows that if we wait around for someone to solve all these problems we'll never get a solution that works. Better to spend some time implementing something with a small set of features that's going to be an improvement to our user base now. Any port that needs the more fancy option setting dialog stuff (as some of them already do) can always override the options: target as necessary. N --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ (__) FreeBSD Documentation Project http://www.freebsd.org/docproj/ \\\'',) \/ \= ^ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- .\._/= _) --cpvLTH7QU4gwfq3S Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj058MkACgkQk6gHZCw343VL0wCfVdotYf67ZyeTbnZjIdWnhma9 WrgAmwVgo/BX5zYubv32BOivT8xld5yW =/p78 -----END PGP SIGNATURE----- --cpvLTH7QU4gwfq3S-- 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?20020720232250.GE37802>