Re: OPTIONS and dynamic PKGNAMPREFIX, e.g. {APACHE, PYTHON, ETC}_PKGNAMEPREFIX (Was: ports/148637 ...)

2010-07-21 Thread Philip M. Gollucci
if USE_APACHE=13 you can write ap13 you know what APACHE_VERSION will evaluate too. Its only vague in the case of a '+' -- 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollu...@p6

Re: OPTIONS and dynamic PKGNAMPREFIX, e.g. {APACHE, PYTHON, ETC}_PKGNAMEPREFIX (Was: ports/148637 ...)

2010-07-21 Thread Philip M. Gollucci
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/21/10 22:06, Anonymous wrote: > UNIQUENAME = ap${APACHE_VERSION}-${PORTNAME} > > and selecting MP4 in www/mod_musicindex it still thinks WITH_MP4 is not > defined. I haven't tried this, but thats a much better attempt then the py- version.

Re: OPTIONS and dynamic PKGNAMPREFIX, e.g. {APACHE, PYTHON, ETC}_PKGNAMEPREFIX (Was: ports/148637 ...)

2010-07-21 Thread Anonymous
"Philip M. Gollucci" writes: > On 07/21/10 20:30, Christopher Key wrote: >> On 19/07/2010 21:05, Anonymous wrote: >>> Christopher Key writes: >>> A crude survey shows several ports with this problem, listed below. >>> ... If you can suggest which is the preferred solution, I'll

Re: OPTIONS and dynamic PKGNAMPREFIX, e.g. {APACHE, PYTHON, ETC}_PKGNAMEPREFIX (Was: ports/148637 ...)

2010-07-21 Thread Christopher Key
On 21/07/2010 21:34, Philip M. Gollucci wrote: -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 writes: A crude survey shows several ports with this problem, listed below. ... If you can su

Re: OPTIONS and dynamic PKGNAMPREFIX, e.g. {APACHE, PYTHON, ETC}_PKGNAMEPREFIX (Was: ports/148637 ...)

2010-07-21 Thread Philip M. Gollucci
-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 writes: >> >>> A crude survey shows several ports with this problem, listed below. >> ... >>> If you can suggest which is the >>> preferred solutio

Re: OPTIONS and dynamic PKGNAMPREFIX, e.g. {APACHE, PYTHON, ETC}_PKGNAMEPREFIX (Was: ports/148637 ...)

2010-07-21 Thread Christopher Key
On 19/07/2010 21:05, Anonymous wrote: Christopher Key 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

Re: OPTIONS and dynamic PKGNAMPREFIX, e.g. {APACHE, PYTHON, ETC}_PKGNAMEPREFIX (Was: ports/148637 ...)

2010-07-19 Thread Philip M. Gollucci
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/19/10 20:05, Anonymous wrote: > Christopher Key writes: > >> A crude survey shows several ports with this problem, listed below. >> There appear to be three different solutions used in other ports: >> explicitly setting OPTIONSFILE, explicitly

OPTIONS and dynamic PKGNAMPREFIX, e.g. {APACHE, PYTHON, ETC}_PKGNAMEPREFIX (Was: ports/148637 ...)

2010-07-19 Thread Anonymous
Christopher Key writes: > A crude survey shows several ports with this problem, listed below. > There appear to be three different solutions used in other ports: > explicitly setting OPTIONSFILE, explicitly setting UNIQUENAME, and > explicitly setting LATEST_LINK. If you can suggest which is th