--Signature=_Sat__24_Jul_2004_07_27_31_+0200_zs7tLMEiBry58fl=
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

On Sat, 24 Jul 2004 15:22:25 +1000
grant beattie <grant@NetBSD.org> wrote:

> I really like this concept. I've often wanted to be able to do just
> this :)
> 
> using PKG_OPTIONS=+ sasl etc.. throughout bsd.pkg.defaults.mk would make
> this more self-consistent and simpler to understand, I think, eg:
> 
> 	# include SASL2 support in packages that support it
> 	PKG_OPTIONS+=	sasl
> 
> 	# include openldap support in packages ...
> 	PKG_OPTIONS+=	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 we'll
have to use something like:

	PKG_OPTIONS+=	databases/openldap security/cyrus-sasl2

Right? or perhaps I'm missing a way to make this automatically without
having to specify the category.

--Signature=_Sat__24_Jul_2004_07_27_31_+0200_zs7tLMEiBry58fl=
Content-Type: application/pgp-signature

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

iD8DBQFBAfNDypkLYVDran0RAut2AJ9R5AsXNSGpl27DTsrOnOzA7p9Y1gCeIV7h
mig++2sZwpCa6zsVh8eNiTM=
=SM3g
-----END PGP SIGNATURE-----

--Signature=_Sat__24_Jul_2004_07_27_31_+0200_zs7tLMEiBry58fl=--