optionsng ignores /var/db/ports/<portname>/options

[Mel Flynn]

On 4-6-2012 0:20, Michael Scheidell wrote:

> optionsng should have been 100% upward compatible.  you should not be
> forced to an an emergency update of a port you maintain just because the
> ports tree broke things.

This has always been broken. It's just exposed by Roland cause he's
/adding/ an option and never had any. graphics/py-yaml has the work
around and it's been there since version 1.14:
<http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/py-yaml/Makefile?annotate=1.20>

(line 25)

The real issue is that something created for slave ports (thus set
before any of the option framework comes in play) is "abused" by Mk/
frameworks that only come in sight /after/ options.mk. This causes two
versions of UNIQUENAME in the execution stream to exist. One before the
framework is included and one after.
-- 
Mel