On Thu, 7 Jan 1999, Todd Vierling wrote:
> : But! I don't know how the current pkg-tools will handle these absolute
> : paths in the PLIST. We'll have to think about that, too, as the config
> : file must be put into the pkgdb as well.
> The intent, as was in the original paths proposal, was not to put any config
> files under direct PLIST control except to copy them in place if they do not
> exist.
> 
> : Maybe some
> : "@conf /etc/foorc share/foo/foorc.conf" command that will DTRT is the best
> : here (copying/backing up if necessary, handling pkgdb, ...).
> 
> Now...  putting this is a pkg databse could be a useful thing, if we were to
> supply a *switch* to pkg_delete that said "delete config files too", but
> would not delete them by default.  Why I hadn't thought of that angle, I
> don't know.

Config files won't be deleted but moved out of the way (possibly if they
have been deleted (md5 is our friend here!), or deleted otherwise (no need
to keep unaltered config files)).


 - Hubert

-- 
Hubert Feyrer <hubert.feyrer@rz.uni-regensburg.de>