On 26/08/2018 18:37, Julien Cristau wrote:
On Sun, Aug 26, 2018 at 12:41:48 +0200, Gioele Barabucci wrote:
the policy lacks guidelines on how to treat user-provided configuration
files during configuration purging in packages for programs that follow the
"stateless" paradigm (default in `/usr`, override in `/etc`). Should they be
removed? Should they be kept?
Second, policy 10.7.3 seems pretty clear to me that purge ought to
remove the package's configuration files, whether they're conffiles or
not.
The question is: what to do with the configuration files of the
_application_ that has not been installed by the _package_?
For instance, apache (the application) is configured by some stub conf
in `/etc/apache` that loads *.conf files from directories such as
`/etc/apache2/sites-enabled/`. The real files are usually in
`/etc/apache2/sites-available/`.
The purge process for the apache (the package) removes the configuration
files it has installed and the symlinks it has created but leaves the
configuration files written by the sysadmin alone.
That seems sensible to me, at least in the cases where there is a clear
cut between package-provided configuration files and user-provided
configuration files for the same application.
Shouldn't it be documented?
Regards,
--
Gioele Barabucci <gio...@svario.it>
