> > Yep. Although the "keeping track of the package manifest" would still > > help a bit there - no protection against clobbering files though. > > What about literally doing that? If one installs a package foo-0.1.spkg, > then a file > > spkg/installed/foo-0.1 > > appears. It could contain a list of all the files that are installed > by foo-0.1. Then uninstall would delete all those files. The only > problem is when a file is in multiple packages; but that is a problem > in most systems.
Good point ! Plus, creating a package manifest in a clean way would have to use DESTDIR or something similar, so it's probably a good way to start. File clobbering would indeed be a problem, but at least it would become detectable before the clobbering. I do think though that the ability to quickly revert an unfortunate upgrade of a (possibly non-optional) package, which would then not be too far away, would be nice to have ... /v --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
