On 03/21/2013 09:20 AM, Nathan Scott wrote:
Mark, I noticed that several files below /etc are marked as
configuration files that seem like they are not - startup
scripts, etc. Marked as such, they need man pages ... do
you recall the reason for tagging them (to rpm) as %config
files? Simplest would seem to be to stop tagging them that
way, but is that valid? (presumably this was done for a
reason back when the rpm packaging was originally done).
$ grep '^%config' build/rpm/SPECS/fedora.spec
%configure --with-rcdir=/etc/rc.d/init.d --with-tmpdir=/var/lib/pcp/tmp
%config %{_sysconfdir}/bash_completion.d/pcp
%config %{_sysconfdir}/pcp.env
%config(noreplace) %{_localstatedir}/lib/pcp/config/pmcd/pmcd.conf
%config(noreplace) %{_localstatedir}/lib/pcp/config/pmcd/pmcd.options
%config(noreplace) %{_localstatedir}/lib/pcp/config/pmcd/rc.local
%config(noreplace) %{_localstatedir}/lib/pcp/config/pmie/config.default
%config(noreplace) %{_localstatedir}/lib/pcp/config/pmie/control
%config(noreplace) %{_localstatedir}/lib/pcp/config/pmie/crontab
%config(noreplace) %{_localstatedir}/lib/pcp/config/pmie/stomp
%config(noreplace) %{_localstatedir}/lib/pcp/config/pmlogger/config.default
%config(noreplace) %{_localstatedir}/lib/pcp/config/pmlogger/control
%config(noreplace) %{_localstatedir}/lib/pcp/config/pmlogger/crontab
%config(noreplace) %{_localstatedir}/lib/pcp/config/pmproxy/pmproxy.options
%config %{_sysconfdir}/pcp.conf
They all look like legit config files to me - an upgrade should not clobber
them if they have local changes. Is that fedora.spec still current? Or did
you mean any other files (or one of the other specs?)? None of the above
seem to be startup scripts (except rc.local, but that's definitely prone
to user customization).
Regards
-- Mark
|