Really, your point is that you can't just install spkg version X on sage version Y. Which is true. Having spkg versions depend on each other makes things even worse. The solution is to keep the spkg build scripts in the same repository as the sage library, so when you checkout Sage (any version) you get the optional packages that have been written for that version. And not the newest spkg version which may or may not work any more on your Sage install.
I understand this is part of the current proposal for the git transition... On Friday, January 11, 2013 11:35:48 PM UTC, Simon King wrote: > > I agree, and had the same problem. The latest released stable Sage > version by default tries to install an spkg that only works in the > current beta release. > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
