From:
[email protected]
On lun, 2004-08-09 at 15:54 -0300, Joey Hess wrote:
That one could be left out then. I have seen .dpkg-old entries under /etc/gconf/schemas on production systems though, so handling .dpkg-old and .dpkg-new seems the right thing to do.
The only reason I can guess why joss made it remove the old files only
on purge is that these were conffiles, and so there could be local modifications that should be preserved. Following this line of thinking, .dpkg-old could have historic information the user wants to keep, and of course the conffiles themselves should be removed only if unchanged.
Indeed, the reason why I didn't remove those files blindly is that they
are conffiles, and the sysadmin may want to see his modifications kept somewhere.
However, I agree that this is minor enough, and we can remove them if
enough people want that. But this is too late for sarge anyway, this is
a decision that affects sarge->sarge+1 migration.
Regards,
--
.''`. Josselin Mouette /\./\
: :' :
[email protected]
`. `'
[email protected]
`- Debian GNU/Linux -- The power of freedom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQBBIQ0+rSla4ddfhTMRAr5oAKDCY9DSTxPZqGYehlcSwhQbzG1WVwCg+ZS5 M/mM4SEmCDLY0prYYE4jLjc=
=Twz+
-----END PGP SIGNATURE-----
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)