Date: Mon, 04 Jun 2012 21:36:35 -0400 From: Greg Larkin <glarkin@FreeBSD.org> To: Roland Smith <rsmith@xs4all.nl> Cc: Matthew Seaman <matthew@FreeBSD.org>, freebsd-questions@FreeBSD.org Subject: Re: [SOLVED] Re: optionsng ignores /var/db/ports/<portname>/options Message-ID: <4FCD62A3.5010301@FreeBSD.org> In-Reply-To: <20120604212543.GA19182@slackbox.erewhon.net> References: <20120603160518.GA6631@slackbox.erewhon.net> <4FCBAA72.7020103@FreeBSD.org> <20120603191003.GA8028@slackbox.erewhon.net> <20120604183234.GC14162@slackbox.erewhon.net> <4FCD1417.4060000@FreeBSD.org> <20120604212543.GA19182@slackbox.erewhon.net>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 6/4/12 5:25 PM, Roland Smith wrote:
> On Mon, Jun 04, 2012 at 04:01:27PM -0400, Greg Larkin wrote:
>>> Well, it was a bug, but not particularly in showconfig alone,
>>> see below.
>>>
>>>>> If not, then something odd is happening, as your port
>>>>> looks perfectly OK to me. Are you using a ports tree
>>>>> updated within about the last 48 hours or so? I know there
>>>>> were some bug fixes went in to all FOO_DESC lines to
>>>>> contain (brackets) and other syntactically significant
>>>>> characters.
>>>>
>>>> I updated my ports tree this afternoon. The really weird
>>>> thing is that I tested 'make config' in several other ports
>>>> where it worked fine...
>>>>
>>>>> PS. Asking this on freebsd-ports@... might be a good idea.
>>>
>>> The bad news is that it was a bug in the ports system. It
>>> turned out that because of the way the unique name of the port
>>> was set (which happens twice), the options file is not read
>>> from the same directory that it is written to! Thanks to
>>> Baptiste Daroussin for clueing me in in this. I've gained a new
>>> respect for the people maintaining the ports infrastructure.
>>> :-) It's kind of amazing it works as well as it does.
>>>
>>> The good news is that there are several workarounds. For
>>> future reference, the workaround that I ended up using was to
>>> set the following variable in the port makefile:
>>>
>>> OPTIONSFILE= ${PORT_DBDIR}/py27-${PORTNAME}/options
>>>
>>>
>>> Roland
>>
>> Hi Roland,
>>
>> I don't think you want to hardcode the "py27-" in the variable
>> assignment, since it ties the filename to a specific version of
>> Python. Check PYTHON_PKGNAMEPREFIX, and it should adjust itself
>> as the Python version changes.
>
> Actually, if I understood correctly, the fact that
> PYTHON_PKGNAMEPREFIX _changes_ from py- to py27- in different parts
> of the included .mk files is what causes the problem in the first
> place. So I did this on purpose.
>
> Roland
Hi Roland,
Ok, I should have read the previous thread emails more closely. At
any rate, putting a specific Python version into the name of the
OPTIONSFILE seems a bit confusing. Could you achieve the same outcome
by putting "py-" instead of "py27-" in the name?
Regards,
Greg
- --
Greg Larkin
http://www.FreeBSD.org/ - The Power To Serve
http://www.sourcehosting.net/ - Ready. Set. Code.
http://twitter.com/cpucycle/ - Follow you, follow me
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk/NYqIACgkQ0sRouByUApBeJACgyuHOEkwVWIdVq31XkLtd89AQ
GWsAoLzZpiKWOAe2u8sEWEM/kGvvnmT+
=JKWu
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FCD62A3.5010301>