On Tue, 24 Oct 2006 14:45:57 -0400 Brad <[EMAIL PROTECTED]> wrote: > On Tue, Oct 24, 2006 at 08:34:37PM +0200, Marc Balmer wrote: > > * Bernd Ahlers wrote: > > > Nikolay Sturm [Tue, Oct 24, 2006 at 07:49:25PM +0200] wrote: > > > >I don't like this. pkg_delete -c should remove as much of a package as > > > >possible. If we know those directories exist, they should be deleted. > > > > > > > >The same goes for mysql and postgresql. If they know where the databases > > > >are, they should delete those directories with "@extraunexec rm -fr > > > >$dir". > > > > > > > But the pkg_delete(1) manpage currently says: > > > > > > -c Delete extra configuration file, mentioned as > > > @extra file > > > in the packing-list. > > > > > > Database data isn't the same as configuration files. (At least for > > > me...) So if we really want the behaviour you're speaking of, the > > > manpage needs an update. > > > > deleting databases whith pkg_delete -c is something I am strongly > > against. The -c is flag is for configuration files. I really do not > > want this behaviour to change, leave it like it is. > > Although the man page does not say so, I have always considered the -c flag > as a package removal "cleaning" flag and that it should remove all files, > not just config files installed into SYSCONFDIR. >
That violates the principle of least surprises. If it is going to delete the data it should clearly say so, anything else will leave users wondering what will get deleted without the flag. The man page should also make clear that data will not be deleted if the "c|D" flag is not supplied.
