[Bug 216585] [PATCH] www/py-pelican: Concurrent install is ineffective without PKGNAMEPREFIX
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sun Jan 29 22:22:29 UTC 2017
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216585
Bug ID: 216585
Summary: [PATCH] www/py-pelican: Concurrent install is
ineffective without PKGNAMEPREFIX
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Keywords: patch
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: jlaffaye at FreeBSD.org
Reporter: john at saltant.com
CC: python at FreeBSD.org
Attachment #179411 maintainer-approval?
Flags:
Keywords: patch
Assignee: jlaffaye at FreeBSD.org
Flags: maintainer-feedback?(jlaffaye at FreeBSD.org)
Created attachment 179411
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=179411&action=edit
www/py-pelican: Set PKGNAMEPREFIX
With the patch in bug #215201 applied, it is possible to build www/py-pelican
with any version of python. However, the fact that USES=concurrent does not, by
itself, allow concurrent installation because the package name is not version
qualified. If PKGNAMEPREFIX is not set, any attempt to install a concurrent
version with pkg will result in a prompt to remove the version already
installed.
The attached patch (which includes the other patch upon which it depends)
changes the package name by setting PKGNAMEPREFIX. A PORTREVISION bump is
appropriate whether or not this patch is committed together with the patch
attached to bug #215201 because of the package name change.
QA
==
portlint: OK
poudriere: OK -- tested on 10.3R amd64 with py27 (default), py34, py35, and
py36
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the freebsd-python
mailing list