On Mon, Mar 30, 2015 at 09:14:40PM +0200, David Naylor wrote: > Hi, > > I am investigating converting my ports to concurrent however I am not sure > how concurrent is supposed to work: > > I looked in /usr/ports/Mk and only found a documentation reference to > 'concurrent'. Setting USE_PYTHON=concurrent doesn't appear to actually > change any behaviour. > > Please could you explain this for me?
From “/usr/ports/Mk/Uses/python.mk”:
concurrent - Indicates that the port can be installed for
different python versions at the same time. The port
is supposed to use a unique prefix for certain
directories using USES=uniquefiles:dirs (see the
uniquefiles.mk Uses for details about the
directories), if set to yes. Binaries receive an
additional suffix, based on ${PYTHON_VER}.
The values for the uniquefiles USES are set as
follows:
UNIQUE_PREFIX= ${PYTHON_PKGNAMEPREFIX}
UNIQUE_SUFFIX= -${PYTHON_VER}
If the port is installed for the current default
python version, scripts and binaries in
${PREFIX}/bin
${PREFIX}/sbin
${PREFIX}/libexec
are linked from the prefixed version to the
prefix-less original name, e.g.
bin/foo-2.7 --> bin/foo.
So it seems that any port that only installs modules in
“/usr/local/lib/pythonX.Y/site-packages/” could be labeled as concurrent as-is.
If your port wants to put things in DOCSDIR, EXAMPLESDIR, DATADIR, WWWDIR or
ETCDIR, you should add “USES=uniquefiles:dirs” to your port's Makefile.
Also read “/usr/ports/Mk/Uses/uniquefiles.mk”.
Roland
--
R.F.Smith http://rsmith.home.xs4all.nl/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 5753 3324 1661 B0FE 8D93 FCED 40F6 D5DC A38A 33E0 (keyID: A38A33E0)
pgpyi9qYxbAuU.pgp
Description: PGP signature
