> > > > I have to say that needing a patch for ''every'' upgrade of a pkg is > > annoying, sage -i should "just work". > > Every upgrade should be reviewed. So, it must not be possible that a >
Sorry, I meant that to upgrade an spkg the end user shouldn't have to do anything. > change in the upstream sources is automatically applied (I guess that's > why spkgs have checksums) without a *reviewed* change (e.g., an update > of the checksums) in Sage. > > However, it *should* be possible to explicitly do > ./sage -i great_package-2.0.0.beta3 > even if "./sage -i gread_package" would install, say, version 1.2.1. > > Best regards, > Simon > > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
