> So what you have in mind is: > > * automatically generate the list of files from *sequential* builds, > store it in spkg (or possibly somewhere else) > > * use this in all default builds (either parallel or sequential), Sage > would store the list of files somewhere, and use it for uninstall > > Is that right? You are right. But I don't see this as the final stage. This is just a step that is slightly less invasive then giving each SPKG it's own version dependent directory in which it can install it's files (like Robert Bradshaw mentioned) so we can have multiple versions of the same SPKG installed and uninstalling is just the removal of a directory. Ofcourse we should also find a solution for the python eggs so that they don't overwrite eachother (maybe use virtualenv or buildout for this).
But as you can see my idea of the final stage is much more involved and has a lot more complications then your simple idea to just keep track of which files belong to which SPKG and create some uninstall based on that. So independent of wathever we might decide that the best final situation might be we should first implement your idea in a parallel build compatible way so we have uninstall. Kind regards Maarten Derickx > > Ondrej -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
