On Thu, 2018-03-15 at 09:43 -0700, Russ Allbery wrote: > Philipp Hahn <pmhahn@pmhahn.de> writes: > > > 3. And/or I can create an additional package "libtirpc-common" to just > > contain that single conffile and make "libtirpc[13]" both depend on it. > > This last option is AFAIK frowned upon as it creates yet another package > > for a single file. > > So whats the current best practice? > > Policy requires 3. Yes, it creates another package, but the ability to > install two versions of a shared library at the same time is vital to how > we do upgrades and is more important than avoiding the occassional extra > package. > > The other option is to version the configuration file so that each SONAME > of the library uses a separate config file, but usually that's worse for > the user and it's better to just have a separate config package. Or you make the configuration file not a conffile. (Then you have the challenge of getting dpkg to forget that it was ever a conffile.) Ben. -- Ben Hutchings Quantity is no substitute for quality, but it's the only one we've got.
Attachment:
signature.asc
Description: This is a digitally signed message part