Hi,
On 05-10-15 11:30, Graham Inggs wrote:
> Hi All
>
> Nico and Felix are seeking guidance on whether to split the Trilinos
> binary packages so that each installs a single shared library or
> whether to lump them all together, as was done in the previous
> packaging (trilinos 10.4.0.dfsg-1, RM'
www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-runtime
[2]
http://anonscm.debian.org/cgit/debian-science/packages/trilinos.git/tree/debian/control
-- Forwarded message --
From: Nico Schlömer
Date: 24 September 2015 at 11:17
Subject: Trilinos: to split or
Nico Schlömer writes ("Re: Fwd: Trilinos: to split or not to split"):
> > "libml.*", really ?
> > I wonder if you need to prefix all of the library names :-/.
>
> We're already considering prefixing them all with "trilinos_".
I guess i
> "libml.*", really ?
> I wonder if you need to prefix all of the library names :-/.
We're already considering prefixing them all with "trilinos_".
--Nico
On Wed, Apr 16, 2014 at 3:16 PM, Ian Jackson
wrote:
> Nico Schlömer writes ("Fwd: Trilinos: to s
Nico Schlömer writes ("Fwd: Trilinos: to split or not to split"):
> Downsides of this include the size of the package, and the fact that
> the package name "trilinos" does not correspond with the library names
> (libbelos.*, libml.*,...).
"libml.*", really ?
Hi Nico,
On Mon, 14 Apr 2014, Nico Schlömer wrote:
> Which approach is better suited for Debian in your opinion?
I think this is in 90% the second option. Only in case that the
libraries used will probably never never never be used outside
the program itself, then it makes sense to keep it in one
On Mon, Apr 14, 2014 at 10:52 AM, Nico Schlömer
wrote:
[...]
> Given its subpackage structure, Felix helped out creating a packaging
> format that splits the build up into subpackages. Debian's shlibs
> magic takes care of the dependency hierarchy, but a couple of things
> problems need to be work
(Forward from debian-mentors.)
Opinion time!
I'm packaging a rather large software, Trilinos, a collection of
libraries (libbelos, libml, libaztecoo,...) for numerical
high-performance computing.
Upstream supports monolithic builds, i.e., the collection of libraries
is assumed to be fully presen
8 matches
Mail list logo