Frédéric Brière <fbri...@fbriere.net> writes: > Yes, that can be easily extracted. I see two issues with this:
> First, there's no guarantee that the file will be the last version > shipped. If a file was included in version X, modified in X+1, and > removed in X+2, it's possible that the user upgraded directly from X to > X+2, and therefore doesn't have the last version of that file. Checking > for the last version is therefore a "best effort", but not foolproof. > (If we really want to nitpick, if the user copied the file contents from > X+1 manually before upgrading to X+2, Policy might possibly require us > to leave that file alone.) > Second, it's quite possible that the file now belongs to another > package, with the exact same contents as our last version of it. I > guess that could be avoided by asking dpkg whether it is currently > owned. > Anybody eager to write that mess of a script? <g> It's not really that much of a mess, but it's kind of annoying and a maintenance hassle. Basically, it's a list of file names and MD5 checksums where if that file name exists and the contents match that MD5 checksum, we remove the file on upgrade. I suspect, though, that we wouldn't want to remove the file if it had moved out of this package into another, which means that it probably wouldn't solve the original problem. And maintaining the list of MD5 checksums is annoying, particularly as you mention if we want to deal with older versions. It would be nice if dpkg provided some clean way of handling this. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
