Date: Tue, 20 Jul 2010 00:05:20 +0400
From: Anonymous <swell.k@gmail.com>
To: Christopher Key <cjk32@cam.ac.uk>
Cc: freebsd-ports@FreeBSD.org
Subject: OPTIONS and dynamic PKGNAMPREFIX, e.g. {APACHE, PYTHON, ETC}_PKGNAMEPREFIX (Was: ports/148637 ...)
Message-ID: <86sk3f5jb3.fsf@gmail.com>
In-Reply-To: <4C44A05B.6040308@cam.ac.uk> (Christopher Key's message of "Mon, 19 Jul 2010 19:58:35 %2B0100")
References: <4C44A05B.6040308@cam.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Christopher Key <cjk32@cam.ac.uk> 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 the
> preferred solution, I'll put together a patch.
They all are workarounds. OPTIONSFILE should be defined *after*
including bsd.{apache,python,etc}.mk so that user can have different
options for different versions of apache/python/etc[1]. Same is true for
UNIQUENAME but it has users under Mk/ directory
(bsd.{databases,tcl}.mk), so it should be defined before them.
I don't know what workaround is preferred but I'd suggest
UNIQUENAME. It's easier to type and has same dependency on
PKGNAMEPREFIX.
[1] For www/mod_musicindex it would be
/var/db/ports/ap20-mod_musicindex/options
/var/db/ports/ap22-mod_musicindex/options
You can't install into same PREFIX because its DATADIR is not apache
version dependant. But many python ports work fine with same PREFIX.
>
> audio/mpdbrowser
> devel/py-gdata
> devel/py-twisted
> graphics/py-pycha
> news/py-pynzb
> security/py-keyring
> www/mod_accounting
> www/mod_dav
> www/mod_limitipconn
> www/mod_musicindex
> www/mod_security
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86sk3f5jb3.fsf>