On Saturday, August 20, 2016, Daniel Holth <[email protected]> wrote: > We have manifests before and after in wheel but good conflict management > is still theoretical. I think someone had a prototype years ago. For > example checking checksums on uninstall and maybe not uninstalling modified > [configuration] files. > - Uninstalling X would break Y and Z - Because there are no additional transitive dependencies, uninstalling X should also uninstall Y and Z - ./etc/x.cfg is modified, don't remove it on_uninstall
> > On Sat, Aug 20, 2016, 15:47 Jim Fulton <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: > >> >> >> On Sat, Aug 20, 2016 at 3:02 PM, Nick Coghlan <[email protected] >> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: >> >> ... >> >> > I have the impression that uninstalling things can be >>> >> > problematic, but maybe that's been fixed. >>> >>> Uninstallation is fine, as we *do* have a full file manifest after a >>> component has been installed. >>> >> >> So, if package A and B install the same file, X, and then A is >> uninstalled, is X still there? If then B is uninstalled, does X go away? >> Does this machinery depend on whether X has the the same contents in A and >> B? >> >> ... >> >> Jim >> >> -- >> Jim Fulton >> http://jimfulton.info >> _______________________________________________ >> Distutils-SIG maillist - [email protected] >> <javascript:_e(%7B%7D,'cvml','[email protected]');> >> https://mail.python.org/mailman/listinfo/distutils-sig >> >
_______________________________________________ Distutils-SIG maillist - [email protected] https://mail.python.org/mailman/listinfo/distutils-sig
