conlict in py-numpy (blocks wspr)

[Roland Smith]

On Tue, Aug 12, 2014 at 05:29:45PM -0400, Diane Bruce wrote:
> ===>   py33-numpy-1.8.1_1,1 depends on shared library: libblas.so - found (/usr/local/lib/libblas.so.2)
> ===>   py33-numpy-1.8.1_1,1 depends on shared library: libumfpack.so - found (/usr/local/lib/libumfpack.so.1)
> ===>  Checking if py33-numpy already installed
> ===>   Registering installation for py33-numpy-1.8.1_1,1
> pkg-static: py33-numpy-1.8.1_1,1 conflicts with py27-numpy-1.8.1_1,1 (installs files into the same place).  Problematic file: /usr/local/bin/f2py
> *** [fake-pkg] Error code 70

It is currently not yet supported to install Python packages for other than
the default Python version.

Recently, changes have been made to the ports infrastructure to allow
installing packages for different (also non-default) versions of Python. From
/usr/ports/CHANGES:

    20140607:
    AUTHOR: mva at FreeBSD.org

    New PYTHON_CONCURRENT_INSTALL knob to support the parallel installation
    of ports for different python versions.

    If set to yes, the knob indicates that the port can be installed for
    different python versions at the same time. The port will use a unique
    prefix for certain directories using USES=uniquefiles:dirs (see the
    uniquefiles.mk Uses for details about the directories). 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.

But the *package tools* don't support this yet. For one of the reasons see
http://lists.freebsd.org/pipermail/freebsd-questions/2013-November/254304.html

    The pkg and ports team is working on fixing package name conflicts in
    the ports tree. Right now packages are identified by their origin in the
    ports tree. Both py27-sphinx and py33-sphinx have the same origin,
    textproc/py-sphinx, so they conflict.

And /usr/ports UPDATING:

  20140307:
  AFFECTS: users of devel/py-setuptools dependent ports
  AUTHOR: sunpoet at FreeBSD.org

  devel/py-setuptools is being used for every python ports (if USE_PYDISTUTILS
  defined) since r336553. Due to PKGORIGIN limitation, we cannot build one
  python port with python27 and the other with python33 since they require
  different setuptools versions which have same PKGORIGIN. With the addition
  of py-setuptools{27,32,33}, we could now have py27-foo and py33-bar coexist
  in one system.

  Note that this is only a short-term solution. It does not help if you need
  coexistence of one port with different python versions, e.g. py27-foo and
  py33-foo.

So this will be fixed in the future.

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)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-python/attachments/20140812/e0e939b7/attachment.sig>