[Nathan Scott] > Upstream have created pcp-zeroconf as a non-default part of the PCP > package suite to automate first-time setup of Performance Co-Pilot for > new users in the same, documented fashion across different distros. > > So while it does indeed not meet the packaging requirements here, it is > not a required part of PCP but a convenience mechanism for new users > who are otherwise overwhelmed with the array of choice and in need of > some assistance as to where / how to start. > > As such, this is operating as intended, designed and documented. Any > users not wanting this behaviour would not opt-in to using this > package.
A policy compliant way to implement this, and one that do not cause unexpected user visible questions about modified conffiles during upgrades, is to teach the program to read configuration from several locations and files, say /usr/share/pcp/config.d/ and /etc/pcp/config.d/, allowing values in /etc/ to override values in /usr/share/, and place the setup provided by the convenience mechanism pcp-zeroconf as a file in /usr/share/. This approach is known as multilevel configuration. I recommend it over modifying conffiles in /etc/. -- Happy hacking Petter Reinholdtsen
