Fwd: Trilinos: to split or not to split
(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 present on the system, and the user picks out
what parts of it he or she wants to use. This makes for a very simple
debian/rules and debian/control, cf.
<https://github.com/nschloe/debian-trilinos/blob/803866a4d552aced1e4b019f1be32217245ce7f4/debian/rules>.
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.*,...).
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 worked around
<https://github.com/nschloe/debian-trilinos/blob/split/debian/rules>.
Which approach is better suited for Debian in your opinion?
Cheers,
Nico
Reply to: