Date: Thu, 9 May 2013 12:47:26 +0100 From: "Steven Hartland" <killing@multiplay.co.uk> To: <ports@freebsd.org> Subject: New Port Options infrastructure bug Message-ID: <9D8B743E1D37426B81B71BD531ABE2E6@multiplay.co.uk>
next in thread | raw e-mail | index | archive | help
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?
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
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337
or return the E.mail to postmaster@multiplay.co.uk.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9D8B743E1D37426B81B71BD531ABE2E6>