Subject: Re: CVS commit: pkgsrc
To: Daniel Carosone <email@example.com>
From: Johnny C. Lam <jlam@NetBSD.org>
Date: 12/22/2004 18:47:19
Daniel Carosone wrote:
> On Wed, Dec 22, 2004 at 09:46:25PM +0000, Johnny C. Lam wrote:
>>Remove support for some variables that are supposed to go away after
>>pkgsrc-2004Q4 is branched.
> As a general question, how do I as an end-user find or get notified of
> these impending changes? I presume I would have to adjust my mk.conf
> accordingly to use the PKG_OPTIONS.* equivalents of my previous
> preferences. Is there a standard notification process in the
> framework (deprecated variable warnings for one release cycle?) or a
> standard location where such changes are documented?
Yes, you would need to adjust your PKG_OPTIONS.* or PKG_DEFAULT_OPTIONS
setting in /etc/mk.conf as a result of this commit.
We can do notification in one of two ways:
(1) If you're tracking -current, you're own your own and it's expected
you'd be tracking pkgsrc-changes anyway, but upon branching, we include
a documentation file that includes a list of removed variables.
(2) We could force some sort of warning to appear during a package build
when a deprecated variable is used, and then after support for that
variable is entirely removed, we remove the warning altogether. The
usual deprecation period is one branch period.
I think the second option is a good way to do this, and I'll look into
providing an easy way for pkgsrc developers to note these deprecated
Thanks a lot for pointing out this very real problem.
-- Johnny Lam <jlam@NetBSD.org>