--F4+N/OgRSdC8YnqX
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Dec 23, 2004 at 12:14:21AM +0100, Juan RP wrote:
> On Thu, 23 Dec 2004 09:45:22 +1100
> Daniel Carosone <dan@geek.com.au> wrote:
>=20
> > On Wed, Dec 22, 2004 at 09:46:25PM +0000, Johnny C. Lam wrote:
> > >=20
> > > Remove support for some variables that are supposed to go away after
> > > pkgsrc-2004Q4 is branched.
> >=20
> > 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?
>=20
> Usually, obsolete variables are documented in the new options.mk file, wh=
en
> the package has been converted.

Ok, thats something.  Is there any facility to learn that the
variables I'm setting aren't being used anymore, and that therefore
the package is suddenly going to be built differently to how I expect
until I make the appropriate change?

As long as they're taking up (comment) space in options.mk, perhaps
something like

PKG_OBSOLETE_VARS+=3DFOO_BAR BAZ

could be used to trip a warning/error and an appropriate generic 'look
in options.mk for clues' message?

--
Dan.

--F4+N/OgRSdC8YnqX
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFBygREEAVxvV4N66cRAuOIAKDJ6phOD+qbjQLzozGrs07BD/hWxgCglzZm
Sz0gCJtJFAEPWSs8oMC4IZ8=
=KGsU
-----END PGP SIGNATURE-----

--F4+N/OgRSdC8YnqX--