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. Anyway, I've cloned the M4RI and M4RIE *SPKG* repositories here: https://bitbucket.org/malb/m4ri-spkg https://bitbucket.org/malb/m4rie-spkg for those who want to play with it. Cheers, Martin -- name: Martin Albrecht _pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99 _otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF _www: http://martinralbrecht.wordpress.com/ _jab: martinralbre...@jabber.ccc.de -- 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
