On Sun, Oct 25, 2009 at 5:20 AM, Simon King <simon.k...@nuigalway.ie> wrote: > > Hi! > > IIRC it is encouraged by the developer guide to inherit from Parent, > Ring, RingElement etc, in order to fit new code cleanly into Sage. But > then, it would be fair to support that an (optional) spkg c-imports > those classes. By "support", I mean that Sage's upgrade script should > do an automatic forced re-installation of an optional spkg if it c- > imports a class from the Sage-tree that changed from one version to > the next (apparently Parent did change in sage-4.2). > > Is such feature already provided? If not, perhaps the following is > doable: spkg-install of some optional package could write its Sage- > tree dependencies into a certain file (I think SAGE_ROOT/spkg/ > installed/ would be a good location). Sage's upgrade script can look > it up and initiate a forced re-installation of the package if needed. > > I think > - it would be useful. I don't know how many optional spkgs c-import > things from sage, but at least mine does. > - it would not interfere with the rule that no spkg should change > things in the sage-tree, since spkg/installed isn't in the sage-tree > - hopefully there is no licence problem. I know that spkg-install > must not be allowed to do a fresh installation of another optional > spkg, since there might be a licence problem (e.g., with the > SmallGroups library). But here I am talking about re-building optional > packages that are already installed - I guess it makes a difference. > > Cheers, > Simon
That sounds like a great idea! Implement it and post a patch. -- William --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
