On Jun 9, 2010, at 4:40 AM, Dima Pasechnik wrote:
Well, I saw upgrades fail repeatedly, and William was writing here that -upgrade is basically not ready for prime time use.
Well, the -upgrade warning is pretty foreboding.
Indeed, one needs to have at least an spkg dependencies mechanism in place, before -upgrade can be done in a fool-proof way. At the moment it is adhoc - an spkg can be checking that another spkg is there and has version at least something, but this is not supported in any consistent way, e.g. like it is done with Debian packages. I.e. there is no declarative facilities in place that would allow one to specify such an interdependency, they rather need to be hard-coded into the spkg install script. So one needs to develop/adopt such a scheme, before -upgrade can be made safe... And I imagine replies here saying that it would increase the complexity of Sage, without adding any new useful functionality. I can only say that in the long term it would save developers time, to have such a scheme in place...
+1 to making up grade work better. It's always worked for me, but I always have a built-from-source Sage on a well supported platform. Are you saying that Makefiles aren't good enough for dependancy checking?
- 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
