[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

**To**:**"Dr. Thomas Orgis" <thomas.orgis%uni-hamburg.de@localhost>****Subject**:**Re: Liblapack.so, libblas.so etc. version numbers? (working on wip/cblas and wip/lapacke)****From**:**Jason Bacon <outpaddling%yahoo.com@localhost>**- Date: Mon, 11 Jun 2018 11:44:17 -0500

On 06/11/18 11:23, Dr. Thomas Orgis wrote:

Am Mon, 11 Jun 2018 11:15:15 -0500 schrieb Jason Bacon <outpaddling%yahoo.com@localhost>:I would be inclined to cooperate with upstream's choice of soversion, but this does present a potential problem of an soversion going backwards with the next update. I'm not sure what the ramifications are for pkgsrc...How is the process to come to a decision there? I must admit that I am not really affected by the update procedure as I always build a fresh pkgsrc tree and keep it that way. IMHO, a switch in the version and an additional symlink libblas.so.4 → libblas.so.3 should work to keep binaries happy. I'll investigate how the cmake build might work for us … not sure yet if all switches are there. Alrigthy then, Thomas

Here's the sum total of committed packages using blas and lapack: [root@centosdev pkg-dev]# pkg-grep blas/build -l|grep -v ^wip biology/mpqc/Makefile biology/plink/Makefile lang/lush/Makefile math/harminv/Makefile math/ipopt/Makefile math/itpp/Makefile math/lapack/Makefile math/octave/Makefile math/py-numpy/Makefile math/py-scikit-learn/Makefile math/R-gstat/Makefile math/R/Makefile math/R-quantreg/Makefile math/R-RandomFields/Makefile math/R-wle/Makefile [root@centosdev pkg-dev]# pkg-grep lapack/build -l|grep -v ^wip biology/mpqc/Makefile biology/plink/Makefile lang/lush/Makefile math/harminv/Makefile math/ipopt/Makefile math/itpp/Makefile math/octave/Makefile math/py-numpy/Makefile math/py-scikit-learn/Makefile math/R/Makefile math/R-quantreg/Makefile

**Follow-Ups**:**Re: Liblapack.so, libblas.so etc. version numbers? (working on wip/cblas and wip/lapacke)***From:*Dr. Thomas Orgis

**References**:**Liblapack.so, libblas.so etc. version numbers? (working on wip/cblas and wip/lapacke)***From:*Dr. Thomas Orgis

**Re: Liblapack.so, libblas.so etc. version numbers? (working on wip/cblas and wip/lapacke)***From:*Jason Bacon

**Re: Liblapack.so, libblas.so etc. version numbers? (working on wip/cblas and wip/lapacke)***From:*Dr. Thomas Orgis

**Re: Liblapack.so, libblas.so etc. version numbers? (working on wip/cblas and wip/lapacke)***From:*Jason Bacon

**Re: Liblapack.so, libblas.so etc. version numbers? (working on wip/cblas and wip/lapacke)***From:*Dr. Thomas Orgis

- Prev by Date:
**Re: Liblapack.so, libblas.so etc. version numbers? (working on wip/cblas and wip/lapacke)** - Next by Date:
**daily pkgsrc CVS update output** - Previous by Thread:
**Re: Liblapack.so, libblas.so etc. version numbers? (working on wip/cblas and wip/lapacke)** - Next by Thread:
**Re: Liblapack.so, libblas.so etc. version numbers? (working on wip/cblas and wip/lapacke)** - Indexes: