Subject: Re: *_OPTIONS for package options
To: Johnny C. Lam <jlam@NetBSD.org>
From: Juan RP <xtraeme@netbsd.org>
List: tech-pkg
Date: 07/24/2004 10:03:46
--Signature=_Sat__24_Jul_2004_10_03_46_+0200_slZ5Y3vSl_jyD.v1
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
On Sat, 24 Jul 2004 07:50:10 +0000
"Johnny C. Lam" <jlam@NetBSD.org> wrote:
> I've attached a file that contains implements this idea. By following
> the example givin in the file, I was able to successfully convert
> several package in my local pkgsrc tree (postfix, mutt-devel, openldap,
> cyrus-sasl, and cyrus-saslauthd) to use this.
Looks good, thanks for the work. But could we have only in the pkg Makefiles:
PKG_SUPPORTED_OPTIONS+= foo bar
And implement the logic automatically, without having to touch the pkg Makefile
for this? I mean, if we add PKG_SUPPORTED_OPTIONS into the pkg Makefile, still
we have to add the logic into the Makefile, right?
I would like to make this automatically, for example as grant said before, e.g:
# package # category #pkg-option
openldap databases ldap
cyrus-sasl2 security sasl2
...
And the logic could be implemented into bsd.options.mk and not into the pkg
Makefile.
What do you think about this?
--Signature=_Sat__24_Jul_2004_10_03_46_+0200_slZ5Y3vSl_jyD.v1
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)
iD8DBQFBAhfnypkLYVDran0RAhcmAJ0QN7Y8CmqHZuUPcH64ZWpw+kn+VgCggnRn
nV1IXYuMAoJfGMxt01fqDDQ=
=reql
-----END PGP SIGNATURE-----
--Signature=_Sat__24_Jul_2004_10_03_46_+0200_slZ5Y3vSl_jyD.v1--