Le 08/24/2010 05:12 PM, M.-A. Lemburg a écrit : > I do see a problem with such a general purpose "conflicts" field, > regardless of what the use case is. If the installer prevents > packages from being installed by means of defining such > a "conflicts" field, this can be used to externally make > package sets incompatible, e.g. a package of > framework 1 could effectively prevent the installation of > a competing framework 2, even though they both can live > happily side-by-side on sys.path. And there's nothing the > authors of framework 2 could do about this. of course, we can force the installation in installers with --force, in such a case, but that's not why the "conflict" field is. Eg. If both can leave together, they're not conflicting :)
Alex _______________________________________________ Catalog-SIG mailing list [email protected] http://mail.python.org/mailman/listinfo/catalog-sig
