Date: Wed, 08 Aug 2012 07:25:01 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Jeremy Chadwick <jdc@koitsu.org> Cc: freebsd-ports <freebsd-ports@freebsd.org> Subject: Re: Questions about/issues with new OPTIONS framework Message-ID: <5022063D.3090106@infracaninophile.co.uk> In-Reply-To: <20120807193029.GA26868@icarus.home.lan> References: <20120806160425.GA23270@icarus.home.lan> <502161C6.70801@FreeBSD.org> <20120807193029.GA26868@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig1AD6574F42AF4D9D825E5318
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On 07/08/2012 20:30, Jeremy Chadwick wrote:
> So it's based off of UNIQUENAME? That's interesting.
>=20
> The ""documentation"" implies that the name of the variable itself
> should be the {nameofport}_SET or {nameofport}_UNSET, where {nameofport=
}
> should equal the name of the actual port directory you're in. Yet, tak=
e
> a look at this:
>=20
> root@icarus:/usr/ports/devel/apr0 # make -V UNIQUENAME
> apr
>=20
> root@icarus:/usr/ports/devel/apr1 # make -V UNIQUENAME
> apr
>=20
> root@icarus:/usr/ports/devel/apr2 # make -V UNIQUENAME
> apr
Actually, there is a set of changes being tested and refined at the
moment to make UNIQUENAME really unique per port. See
http://people.freebsd.org/~matthew/uniquename/uniquenames.diff
for example. PR ports/148637
Which means that those ports will have UNIQUENMES of apr0, apr1 and apr2
respectively, and the MySQL ports:
> root@icarus:/usr/ports/databases/mysql55-server # make -V UNIQUENAME
> mysql
>=20
> root@icarus:/usr/ports/databases/mysql55-client # make -V UNIQUENAME
> mysql55-client
would use mysql55-server and mysql55-client respectively.
Actually, that raises an important point, because the constructed
variable names like 'mysql55-client_SET' should perhaps have
syntactically significant characters like '-', '+' mapped to '_'
One intended consequence of this change is that ports which have
accidentally ended up using the same OPTIONSFILE now no-longer will.
Where it is desired for ports to share the same OPTIONSFILE, as in the
case of mysql55-server and mysql55-client then those ports will have to
have explicit settings to enable that.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matthew@infracaninophile.co.uk Kent, CT11 9PW
--------------enig1AD6574F42AF4D9D825E5318
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlAiBkYACgkQ8Mjk52CukIwoXQCdEqz4nVyO7ZJDim1tixVYRGCj
tFIAn13qeYeiYdMR+l/9Ibo09o1NEqIG
=JpDE
-----END PGP SIGNATURE-----
--------------enig1AD6574F42AF4D9D825E5318--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5022063D.3090106>