On Dec 8, 2008, at 1:11 PM, root wrote: > >> What about an option to the upgrade script, e.g. >> >> sage -upgrade [-b branch] >> >> which would upgrade specified branch inplace if specified? > > I don't want to start a religious war but this is trivial in > a git repository. There was some talk a while back about changing > to git.
No, using git or mercurial as the underlying RVC has little to do with this. Sage has half a dozen repositories (though thankfully that number is going down) and 100+ other packages. The "branches" referred to here are entirely separate copies of the repo (which has its advantages and disadvantages, especially due to the fact that there are a lot of un-checked in intermediate files that require a non-trivial amount of time to regenerate, but that's been covered before). The -upgrade script is about downloading and building all the separate components that need to be updated. The question here is not how to upgrade a repository, but whether or not the -upgrade script should automatically merge the new changes on top of a modified repository (silently braking things when there's a conflict) or require the user to do so manually. - Robert --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
