+1 from me, for exactly the reasons Martin gives.   When I am making a
new eclib spkg (as I am now) I waste time sorting through all the old
ones littering my computers.  But one can always just unpack the spkg
in the latest Sage (devel) release -- is what is being proposed any
easier?

John

On 15 April 2012 14:40, Keshav Kini <keshav.k...@gmail.com> wrote:
> Martin Albrecht <martinralbre...@googlemail.com> writes:
>
>>> If, as I infer from your wording, you propose consolidating all the SPKG
>>> repos into a single repo,
>>
>> No! Not at all. This might be good or bad down the road, but I am definitely
>> not proposing this now. Instead I say we should keep canonical copies of each
>> SPKG repo somewhere online to avoid screw ups like I do them all the time.
>> This change would very much not intrusive: we could switch over SPKGs one by
>> one etc.
>
> Oh, in that case that is a very inoffensive suggestion, +1 from me :)
> Though IIRC Jeroen's scripts make commits to SPKG repos automatically so
> you might want to hear some feedback from him... luckily he is already
> on this thread.
>
> -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

-- 
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

Reply via email to