[Debian-med-packaging] Bug#994551: libcifpp1: please split off static files to separate package
Andrius Merkys
merkys at debian.org
Fri Sep 17 16:43:28 BST 2021
Package: libcifpp1
Version: 1.0.1-3
Severity: serious
Hello,
I have just noticed that libcifpp1 violates section 8.2 of Debian policy:
> If your package contains files whose names do not change with each
> change in the library shared object version, you must not put them in
> the shared library package. Otherwise, several versions of the shared
> library cannot be installed at the same time without filename clashes,
> making upgrades and transitions unnecessarily difficult.
So far, there has not been other libcifppX binary package, thus no
damage is done. However, future libcifppX packages should not contain
static files, in particular these:
/etc/cron.weekly/libcifpp
/usr/share/libcifpp/isomers.txt.gz
/usr/share/libcifpp/mmcif_ddl.dic.gz
/usr/share/libcifpp/mmcif_pdbx_v50.dic.gz
I suggest splitting them off to a separate Architecture: all package,
for example, libcifpp-data. This package would then be responsible for
keeping mmCIF dictionary via cron, and other packages requiring these
dictionaries would then depend on libcifpp-data.
Andrius
More information about the Debian-med-packaging
mailing list