[nycbug-talk] Re: confusion with NetBSD's PKG_OPTIONS
Mon Jan 2 16:20:51 EST 2006
-----BEGIN PGP SIGNED MESSAGE-----
On Mon, Jan 02, 2006 at 03:25:03PM -0500, Amitai Schlair wrote:
> On Jan 2, 2006, at 3:22 PM, Scott Robbins wrote:
> >According to that page on pkgsrc, using mk.conf for this is deprecated.
> >On the other hand, many knowledgeable NetBSD folks seem to feel that
> >putting these things in mk.conf is the best idea.
> It's definitely not deprecated! Can you point me at the page where you read
> that, so we can fix it?
(sorry about the wrap)
If you are part of the NetBSD documentation team, then may I suggest
putting in a few examples?
Actually, I see that rereading it (when I read it last night it was
quite late) the actual wording is.
efore the options framework was introduced, build options were selected
by setting a variable in /etc/mk.conf for each option. To ease
transition to the options framework for the user, these legacy variables
are converted to the appropriate options setting automatically. A
warning is issued to prompt the user to update /etc/mk.conf to use the
options framework directly. Support for these legacy variables will be
I took that to mean that setting them in mk.conf was deprecated, but I'm
putting that down to it being very late at night when I read it.
A bit of experimentation indicates that in mk.conf, if you use " " you
get an error message. For example, if I wanted to include the
non-default eb and not include canna, my mk.conf entry would be
Again, I think examples would be extremely helpful to the reader.
PGP keyID EB3467D6
( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
gpg --keyserver pgp.mit.edu --recv-keys EB3467D6
Angelus: I wanna torture you. I used to love it, and it's been
such a long time. I mean, the last time I tortured someone, they
didn't even *have* chainsaws.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)
-----END PGP SIGNATURE-----
More information about the talk