Martin Albrecht <martinralbre...@googlemail.com> writes: > Hi, > > I don't know about you, but I screw up surprisingly often when it comes to > cutting SPKGs (starting off from old versions, copying wrong files etc.). > > I figured perhaps we should make use of the repositories we have inside the > SPKGs already. The idea being that all changes to SPKGs are pushed to some > repository on the net and this way it's much much easier to cut fresh SPKGs > (which can be automated actually). > > Do people think it's a good idea and we should adopt this strategy for SPKGs? > I think it would make things much easier and less error prone.
If, as I infer from your wording, you propose consolidating all the SPKG repos into a single repo, then you might be interested in what R. Andrew Ohana and I did in the last few days of Review Days 2 last month - see http://github.com/kini/sage-workflow . The SEP draft there is very far from complete, and we (and others who were there) did brainstorm more ideas than appear in that document right now, so it's probably best to just ignore that document for the moment - which is why I haven't really posted about it on sage-devel yet. But the shell script `consolidate-repos.sh` could be interesting to you. -Keshav ---- Join us in #sagemath on irc.freenode.net ! -- 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
