Re: Statically linked library in libdevel packages? (Was: Status of teem package (packaging moved from svn to git))
On 28/01/16 16:27, Christian Seiler wrote:
> So unless there is an _undue_ maintenance burden for building a static
> version of a given library
... or a reason why it's useless. For instance,
src:telepathy-mission-control-5 ships libmission-control-plugins, which
could easily be built static but there's no point (it's only used for
plugins into a specific executable).
I expect this is quite rare, though. A similar arrangement is basically
only necessary for projects that support being built for Windows (where
plugins normally have to have all their dependencies satisfied by
libraries) and want to use the same build rules everywhere, or for
projects that verify self-containedness of all objects as a QA tool.