Subject: Re: *_OPTIONS for package options
To: Juan RP <email@example.com>
From: grant beattie <firstname.lastname@example.org>
Date: 07/24/2004 15:36:08
Content-Type: text/plain; charset=us-ascii
On Sat, Jul 24, 2004 at 07:27:31AM +0200, Juan RP wrote:
> > # include SASL2 support in packages that support it
> > PKG_OPTIONS+=3D sasl
> > # include openldap support in packages ...
> > PKG_OPTIONS+=3D openldap
> > or something similar. what do you think?
> That sounds better than Johnny's suggestion IMO :)
> But how do you know which category will use every package? I think that w=
> have to use something like:
> PKG_OPTIONS+=3D databases/openldap security/cyrus-sasl2
> Right? or perhaps I'm missing a way to make this automatically without
> having to specify the category.
I imagine there would be a defined list of valid _OPTIONS values
corresponding to packages that have had support for global options
added, so the category doesn't need to be exposed to the user at all -
but I'm speculating ;)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)
-----END PGP SIGNATURE-----