On Tue, Mar 6, 2012 at 10:18 PM, John H Palmieri <jhpalmier...@gmail.com> wrote: > > > On Tuesday, March 6, 2012 4:35:45 PM UTC-8, R. Andrew Ohana wrote: >> >> It seems odd to me that the extcode and sage_scripts spkgs have their >> version bumped with every sage release. sage_scripts contains the >> version info for sage (in sage-banner), but IMO this is something that >> should be stored in the root repo (maybe as environmental variables in >> sage-env). Other than that, these two spkgs are touched relatively >> infrequently, so it seems silly to me that we version bump these spkgs >> for no apparent reason. >> >> Ticket #10231 (which is about this) was set to sage-pending due to >> debate on this mailing list, is there still support for this seemingly >> arbitrary version bumping? > > Another proposal made on this list was to merge the main Sage repo with the > scripts and extcode repositories, and I would add the root repository also. > (I think that extcode could also use a lot of cleaning up.) What about that > plan? > > It might be a fine idea to stop bumping up the versions, but > > - it is mainly cosmetic, I think, so > - it seems pretty low priority among possible modifications to Sage, and > - if we might change the structure of the repositories, say by merging > them, why put much work into modifying the version numbers? > - Keshav has also proposed merging all of the repositories for the spkgs > into a single repository. This is also an interesting idea. How would that > fit in? > > It makes more sense to me to have a discussion about the general structure > of the repositories in the Sage distribution, rather than focus on one small > aspect of that: the version numbers of a few repositories. Why paint the > bike shed when we might just knock it down in a few months?
+1 I might also add that these commits are the only record (aside from the full release tarballs themselves) of which version of scripts, etc. corresponded to which version of the Sage release. I'd also find it strange (and a bit disconcerting) to have sage_scripts-4.7.1.spkg and sage-root-5.0.spkg shipped with sage-5.1.spkg, but this is all cosmetic and fairly inconsequential compared to the significant improvements we could make with larger-scale refactoring of the repositories. - Robert -- 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
