Package: pcp Version: 3.5.11 The way libpcp3 is packaged has the potential to cause problems down the track. In particular, the shared library package contains both the (SONAME versioned) library files and configuration files (pcp.conf, and builddefs/buildrules) in the same package.
The problem is if/when we move to a libpcp4 package, this will not be able to be installed at the same time as libpcp3 (which is a major advantage of the Debian shared library packaging, when done correctly). This is because /etc/pcp.conf and some other files will conflict between the packages. Discussion with Julien Cristau (jcris...@debian.org) in the context of bug 654616, where further discussion on this topic can be found, identified three potential ways to address the problem, paraphrased as: 1. make libpcp.so not require pcp.conf (and probably move it to pcp package) 2. create a separate package for the configuration files (these are the core config files - i.e. pcp.conf - and also the builddefs/buildrules files needed by the layered -dev development packages). 3. use SONAME-specific file names in libpcp3 for the config files (/etc/pcp3.conf) This obviously needs to be addressed before any libpcp4 can ever exist. Its not on the immediate horizon, but pcpv4 plans are well underway and it might well be needed in the medium term. Best to tackle it sooner rather than later anyway. In #654616 I lay out a preference for option #2 but I'll seed feedback from other interested / knowledgeable parties before going far down any particular path. cheers. -- Nathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
