Hi Alastair,
On Sun, Feb 14, 2016 at 08:44:48PM +, Alastair McKinstry wrote:
> I've been investigating and libncl.a does not directly get used by any
> other package associated with NCL-ncarg; there is a shared-object
> variation but its called libNGncl.so.1
> which won't conflict. libncl.a ge
Hi,
I've been investigating and libncl.a does not directly get used by any
other package associated with NCL-ncarg; there is a shared-object
variation but its called libNGncl.so.1
which won't conflict. libncl.a gets used by ncargf77 and libncargf90
wrappers (and newer pkg-config versions) that set
Hi Paul,
I'm sending this to you to get you in the loop [see thread below] on a
name conflict for the NCL.
Both "ncl" and "nexus" are used by other libraries.
Perhaps phylo-ncl or phylo-nexus could work.
(or of course, it could be left to users of debian to compile from source).
all the best,
Mar
Hi Mark,
thanks a lot for the ultra fast response.
Could you come up with a better renaming suggestion and may be also put
the original author in CC?
Its to bad to have two different scientific data formats with the same
name. I wonder whether there is some typical prefix of suffix to
different
Hi Mark,
the Debian Med team has packaged your NCL library for the Debian
distribution. We received a bug report that there is a naming conflict
with
http://www.ncl.ucar.edu/
My suggestion to solve this conflict would be to rename libncl to
libnexus. In my opinion it would make sense to re
Package: libncarg-dev,libncl-dev
Version: libncarg-dev/6.3.0-6+b1
Version: libncl-dev/2.1.18+dfsg-2
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Date: 2016-02-07
Architecture: amd64
Distribution: sid
Hi,
automatic installation tests of packages that share a file and a
6 matches
Mail list logo
