Date: Mon, 4 Jun 2012 23:25:43 +0200 From: Roland Smith <rsmith@xs4all.nl> To: Greg Larkin <glarkin@FreeBSD.org> Cc: Matthew Seaman <matthew@FreeBSD.org>, freebsd-questions@FreeBSD.org Subject: Re: [SOLVED] Re: optionsng ignores /var/db/ports/<portname>/options Message-ID: <20120604212543.GA19182@slackbox.erewhon.net> In-Reply-To: <4FCD1417.4060000@FreeBSD.org> References: <20120603160518.GA6631@slackbox.erewhon.net> <4FCBAA72.7020103@FreeBSD.org> <20120603191003.GA8028@slackbox.erewhon.net> <20120604183234.GC14162@slackbox.erewhon.net> <4FCD1417.4060000@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--zhXaljGHf11kAtnf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
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.
> >=20
> >>> 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.
> >>=20
> >> 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...
> >>=20
> >>> PS. Asking this on freebsd-ports@... might be a good idea.
> >=20
> > 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.
> >=20
> > 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:
> >=20
> > OPTIONSFILE=3D ${PORT_DBDIR}/py27-${PORTNAME}/options
> >=20
> >=20
> > Roland
>=20
> Hi Roland,
>=20
> 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
--=20
R.F.Smith http://rsmith.home.xs4all.nl/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
--zhXaljGHf11kAtnf
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)
iEYEARECAAYFAk/NJ9cACgkQEnfvsMMhpyUUGwCgroUMig7A1BSDplILsgwwb9HM
f0UAniDua8dw40qLZvQ3cf92ySuKgxZk
=ldPe
-----END PGP SIGNATURE-----
--zhXaljGHf11kAtnf--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120604212543.GA19182>