Date: Tue, 31 Mar 2015 21:39:37 +0200 From: David Naylor <dbn@freebsd.org> To: Roland Smith <rsmith@xs4all.nl> Cc: freebsd-python@freebsd.org Subject: Re: USE_PYTHON=concurrent Message-ID: <3956416.IomzSLxEPG@dragon.local> In-Reply-To: <20150331184738.GA95383@slackbox.erewhon.home> References: <3945228.UPHqZybedq@dragon.local> <20150331184738.GA95383@slackbox.erewhon.home>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
On Tuesday, 31 March 2015 20:47:38 Roland Smith wrote:
> 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”.
Thank you for your explanation, to confirm:
So 'concurrent' shouldn't actually change any logic, but act as a flag for a
build tool at actually build multiple versions of the port based on available
and supported python versions? (However one might need to use uniquefiles to
prevent file conflicts with the multiple packages from this port.)
Regards
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQJ8BAABCgBmBQJVGvf5XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ5NDhFQzUxMUEyN0YwMzAyRTc5OUI1M0FB
RDYzRkE4REQ2QjJEQTU1AAoJEK1j+o3WstpVqpcQAKcSEvTuP9DV68h852Mc0oWi
F0/PfvHe/Cu39G99+Gw9zLtUtdHW6zWh31CziRZLdnx0VfLq9asFR7pyR0ti1jTy
FZp22bgLV8dqyDeFsdE6mxK6+GTtZ8HOfxsqeWF42xl7J/j4U5pK1YNn0I76o/UY
pwMHJStA9VgbROVE+9/KkGdWCangIISXlo2cl6zM4CGfF2bZM/wlgOYdQcZR/Fd9
DEytviCfl5fEJ/u41773cSQCMFKxB/xGbuGUHlqhd5OyOrOg18xJkSszMS/abmDy
Jhw9sB2GUut6VrmEJksju6Zti5ZcQOYyRzB9HuS3Idhbs+lb6h873iSY5XWBhm8c
U142MvX24Y9DV7xSfJbY0fk68j9XjzxdCYb19hen8l27ILz3VpvYHCOoqTkG1wT/
58mpQ/EazLXSiddpxDDmuxkUsF8QA3POLsYZObQ3pRM6jm/ViY9KF4xg7pK49H9Y
N45chcUhLTmpQOdYv+4OnO403aLWIPpPhBEK2keNeavqoaEW59QwVmnu6H7aKs47
Dn+MTktGACySrIwOp61X+zy8/F86n+ndtNy+klLpaUzZGmIH2bkufms7U4bDb0Af
ERbyZywRNWF3SBl2XbAiDbc9H7i6PynSrKwpcXREiUEHXurcYEPGEaPJv/+9zMHk
M0LZ0C89qdJ9MDDp6YjY
=MHR1
-----END PGP SIGNATURE-----
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3956416.IomzSLxEPG>