--Vhqu5qQ3bjg0ZI9i
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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
> >=20
> > 	# include openldap support in packages ...
> > 	PKG_OPTIONS+=3D	openldap
> >=20
> > or something similar. what do you think?
>=20
> That sounds better than Johnny's suggestion IMO :)
>=20
> But how do you know which category will use every package? I think that w=
e'll
> have to use something like:
>=20
> 	PKG_OPTIONS+=3D	databases/openldap security/cyrus-sasl2
>=20
> 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 ;)

grant.


--Vhqu5qQ3bjg0ZI9i
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iD8DBQFBAfVIluYOb9yiFXoRAjVuAJ4jxeyjwHTm3mInEZlXzCdMwzCXYwCgnweE
Sh4jy5pyJPUOAfci1Kwv8Js=
=sbnU
-----END PGP SIGNATURE-----

--Vhqu5qQ3bjg0ZI9i--