Date: Wed, 21 Jul 2010 20:34:46 +0000
From: "Philip M. Gollucci" <pgollucci@p6m7g8.com>
To: Christopher Key <cjk32@cam.ac.uk>
Cc: Anonymous <swell.k@gmail.com>, freebsd-ports@freebsd.org
Subject: Re: OPTIONS and dynamic PKGNAMPREFIX, e.g. {APACHE, PYTHON, ETC}_PKGNAMEPREFIX (Was: ports/148637 ...)
Message-ID: <4C4759E6.1030305@p6m7g8.com>
In-Reply-To: <4C4758FA.2030607@cam.ac.uk>
References: <4C44A05B.6040308@cam.ac.uk> <86sk3f5jb3.fsf@gmail.com> <4C4758FA.2030607@cam.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/21/10 20:30, Christopher Key wrote:
> On 19/07/2010 21:05, Anonymous wrote:
>> Christopher Key<cjk32@cam.ac.uk> writes:
>>
>>> A crude survey shows several ports with this problem, listed below.
>> ...
>>> If you can suggest which is the
>>> preferred solution, I'll put together a patch.
>>
>> I don't know what workaround is preferred but I'd suggest
>> UNIQUENAME. It's easier to type and has same dependency on
>> PKGNAMEPREFIX.
The mod_* ports should not be py-* prefixed.
If you're going to do it, they should he ap${APACHE_VERSION}- prefixed.
Several ports show examples of this already. Also, AP_FAST_BUILD does
this for you.
- --
- ------------------------------------------------------------------------
1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C
Philip M. Gollucci (pgollucci@p6m7g8.com) c: 703.336.9354
VP Apache Infrastructure; Member, Apache Software Foundation
Committer, FreeBSD Foundation
Consultant, P6M7G8 Inc.
Sr. System Admin, Ridecharge Inc.
Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (FreeBSD)
iD8DBQFMR1nmdbiP+9ubjBwRAkAAAKCBUzmWCcvji68JW8jInXEe+lFwIgCfbEfT
WdFLDLv4vO/18qvF2NuAqzg=
=PHi+
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C4759E6.1030305>