Date: Tue, 5 Jun 2012 07:48:42 +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: <20120605054842.GA21247@slackbox.erewhon.net> In-Reply-To: <4FCD62A3.5010301@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> <20120604212543.GA19182@slackbox.erewhon.net> <4FCD62A3.5010301@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--DocE+STaALJfprDB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 04, 2012 at 09:36:35PM -0400, Greg Larkin wrote: > >> Hi Roland, > >>=20 > >> I don't think you want to hardcode the "py27-" in the variable=20 > >> assignment, since it ties the filename to a specific version of=20 > >> Python. Check PYTHON_PKGNAMEPREFIX, and it should adjust itself > >> as the Python version changes. > >=20 > > 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. > >=20 > > Roland >=20 > Hi Roland, >=20 > 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.=20 OTOH, it keeps the name of /var/db/port/<name>/options in line with the packagename (without the version number), and it is what most Python-based ports seem to do. > Could you achieve the same outcome > by putting "py-" instead of "py27-" in the name? Yes, more or less. There are ports that do that as well. But the majority s= eem to include the python version. AFAICT to be able to install the same package with different options for different Python versions.=20 Anyway, the PR for updating my port is out. And one of the maintainers is working on some of the warts of the ports system. It turns out that this bug was already reported two years ago. But the ports system is quite a complex beast... =20 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) --DocE+STaALJfprDB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAk/NnboACgkQEnfvsMMhpyUmrQCbBdFy8nI/IsBzbTgLeaQwtDHL r/cAoKRy+WGK3xIfvTEaMQosHRJ8ImHY =zvS0 -----END PGP SIGNATURE----- --DocE+STaALJfprDB--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120605054842.GA21247>