New Port Options infrastructure bug

[Jeremy Messenger]

On Thu, May 9, 2013 at 6:47 AM, Steven Hartland <killing at multiplay.co.uk> wrote:
> I've just been looking at devel/rubygem-multi_json and was
> perplexed by how it wasn't saving my options.
>
> It seems that how the new port options infrastructure determines
> where to load and store its configured options from is quite
> flaky and breaks with anything that amends PKGNAMEPREFIX within
> a sub Makefile such as python, ruby etc.
>
> Having searched long for the issue it seems lots of ports
> are having to work-around this problem as indicated by
> comments such as:-
>
> # bypass infrastructure bug (taken from www/py-django)
> OPTIONSFILE=    ${PORT_DBDIR}/py-${PORTNAME}/options
>
> Is this a know issue which has someone is working on it or are
> port creators being left deal with this on a case by case
> basis?

See here: http://lists.freebsd.org/pipermail/freebsd-ports/2013-April/083035.html

I don't really have much of time to create patch and test until
somewhere in June.

> Obviously its extremely frustrating from a user perspective
> to find out that the options chosen aren't actually being
> applied as they are failing to save / load :(
>
>    Regards
>    Steve


--
mezz.freebsd at gmail.com - mezz at FreeBSD.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/ - gnome at FreeBSD.org