At 08:32 AM 5/15/2009 +0200, Tarek Ziadé wrote:
2009/5/15 P.J. Eby <p...@telecommunity.com>:
> Ideally, a file with identical size/checksum that
> belongs to more than one project should be silently left alone, and a file
> installed by more than one project with *different* size/checksum should be
> warned about and left alone.
I think the path is the info that should be looked at.
By "a file that belongs to more than one project" I meant a single
file on *disk* (i.e., one absolute path).
But I don't think you want to leave alone a file with identical
size/checksum that belongs to more than one project when it's not
the same absolute path.
That wouldn't be "a file" then, would it? ;-)
Here's an example why : if two different packages includes the
"feedparser.py" module
(from the FeedParser project) for conveniency, and if you remove one package,
you *do* want to remove its "feeparser.py" module even if it exists
in the other
project.
Right, that would be *two files*, though, not one file.
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
