[Bug 211768] [NEW PORT] net/py-mpi4py-{openmpi,mpich2}
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Fri Aug 12 11:20:10 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211768
Kubilay Kocak <koobs at FreeBSD.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |maintainer-feedback?(mike.d
| |.ft402 at gmail.com)
CC| |koobs at FreeBSD.org,
| |mike.d.ft402 at gmail.com
Keywords| |feature, needs-qa, patch
Status|New |Open
Assignee|freebsd-ports-bugs at FreeBSD. |python at FreeBSD.org
|org |
--- Comment #12 from Kubilay Kocak <koobs at FreeBSD.org> ---
Thank you Michael:
A few initial review items:
Apart from the MASTER port portlint warning, the other portlint warnings should
be addressed, in particular the two FATAL's.
PYSETUP in do-test should be PYDISTUTILS_SETUP
I don't entirely understand why there are two separate ports (thus packages)
here, given:
- Upstream provides instructions to just pip install mpi4py
- Ports should be named according and only to the upstream (PyPI) name unless
there's a compelling case to do otherwise.
- The two ports conflict
If it because there are two 'versions' depending on the MPI library that is
available, then the port should be:
- PORTNAME=mpi4py
- With multiple (two) mutually exclusive "MPI Backend" OPTIONS
- With a suitable (matching upstream) OPTIONS_DEFAULT on one of them
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-python
mailing list