-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/27/2013 05:09 PM, Eitan Adler wrote:
> Can anyone on this list please review the following. I am not certain
> it is good advice.
>
> diff --git a/en_US.ISO8859-1/books/porters-handbook/book.xml
> b/en_US.ISO8859-1/books/porters-handbook/book.xml
> index 0f7d8c6..423bd80 100644
> --- a/en_US.ISO8859-1/books/porters-handbook/book.xml
> +++ b/en_US.ISO8859-1/books/porters-handbook/book.xml
> @@ -7603,6 +7603,11 @@ _DOCSDIR= .
>
> <programlisting>PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX}</programlisting>
>
> + <para>Generally, if <makevar>PKGNAMEPREFIX</makevar> is set, the
> + port requires a <literal>py-</literal> origin prefix:
> + For example,
> +
<filename><replaceable>sysutils/py-myport</replaceable></filename></para>
> +
> <table frame="none">
> <title>Most Useful Variables for Ports That Use Python</title>
>
The preceding paragraph already states the really important bit.
"Ports that install files under PYTHON_SITELIBDIR should use the pyXY-
package name prefix, so their package name embeds the version of Python
they are installed into."
In principle, this allows the user to maintain two or more concurrent
versions of Python, and install a given port for each one. If the
versioned PKGNAMEPREFIX is omitted, then concurrent installs of the port
don't work.
So, does the use of PKGNAMEPREFIX generally require "py-" in the origin?
No. What undesirable thing happens if I use the former, but omit the
latter? Nothing, as far as I know. It's certainly a convention, and, I
think most would agree, a useful one, but we should crispy distinguish a
requirement ("Do this!") from a best practice ("Most people do this.").
How many ports use PKGNAMEPREFIX, but aren't named $CATEGORY/py-$PORT?
% find /usr/ports -depth 2 -name "py-*" -prune -o -depth 3 -type f -name
Makefile \
| xargs egrep "^PKGNAMEPREFIX=.*PYTHON_PKGNAMEPREFIX" -l \
| wc -l
51
How many ports are named $CATEGORY/py-$PORT, but don't use PKGNAMEPREFIX?
% find /usr/ports -path "*/py-*" -name Makefile \
| xargs egrep "^PKGNAMEPREFIX=.*PYTHON_PKGNAMEPREFIX" -L \
| wc -l
30
Is this OK? Yes, it is.
Regards,
John
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iQEcBAEBAgAGBQJRLrJxAAoJEEdKvTwaez9wAJUIAMfQrL6VV7Px760Nre6v5WJo
vUN1tA9+5wHylNNLsO2miM0MCOBxgym3RhF+maQ5T00dLaunrgIDjJVvOWE42SzI
cIUgETxIcqMlyHaE1yWzzLihxxYruo1IMQvaOvbjCg3euCoPeK3XXA4D7Ro9V647
ZtYfP3KKOtgcHlVAp1oWcD2A402nu1rJeHDyN4ezr5Jae+FdCwvwWgZZyT3Pc0og
MwFgcWGhPkODMwTBqOfAiN3qjWX65FBFus2y6h6i4NIdNQ+gr3VXKuOYcwDQS8tB
iDzAjZ9MN7312vlm7zXny4V0j3z3MZYMr0Y+NCfBjk8ZYns7/6qDxaMp8TR7gPg=
=fpt8
-----END PGP SIGNATURE-----
_______________________________________________
freebsd-python@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
