On Sep 2, 2005, at 9:59 AM, Jeroen Ruigrok/asmodai wrote:

> -On [20050902 15:36], Jeroen Ruigrok/asmodai (asmodai@in-nomine.org) 
> wrote:
>> I got interested in how the deprecated options got handled when it 
>> seemingly
>> seems not to reflect a pkg reality.
[...]
> mk/djbware.mk:DJB_ERRNO_HACK?=    YES
>
> Which will cause: Deprecated variable DJB_ERRNO_HACK used, use
> PKG_DEFAULT_OPTIONS+=djbware-errno-hack instead.
> for about 10 pkgs.
>
> The entire DJB_ERRNO_HACK variable can be nuked anyway:
>
> within pkgsrc: $ grep -R DJB_ERRNO_HACK *
> mk/djbware.mk:DJB_ERRNO_HACK?=  YES
> mk/djbware.mk:PKG_OPTIONS_LEGACY_VARS+= 
> DJB_ERRNO_HACK:djbware-errno-hack

The reason there's still code to deal with this variable, and the 
others you mentioned, is that people may have chosen to set them in 
mk.conf. We generally keep honoring such deprecated variables until 
after the next quarterly pkgsrc branch has been cut.

- Amitai