> Last August, I released the first version of my slabbe-0.1.spkg. I had to > choose at that time between the old-style and the new style. I explained > here [1] why I finally choose the old-style. If I use the new style and I > release slabbe-0.2 tomorrow during a conference let say for fixing a bug > found by a colleague, then the version 0.2 won't install on the sage > installation of my colleague. Why? The checksums need to be updated. And, I > want it to be a simple installation one liner like "sage -i > slabbe-0.2.spkg" that anybody can do. That is why I believe that old style > is still usefull for packages farther from sage (my package is not listed > anywhere I think). > >>
> > Are you meaning that you still update it as an “old” spkg? >> >> Yes. Reason? Hm. The best reason I have is this: The code in the spkg >> has never been published elsewhere, and thus I think that the spkg *is* >> upstream. Somebody told me that I should post the code somewhere on >> github. But then I think this would be an artificial complication. >> Moreover, I plan to migrate the code of the spkg to the Sage library; if >> this will be done, the optional spkg will only be useful to do >> cross-verifications of computations, and will not be further maintained. >> > Well, that's two people already... For the time being perhaps one can change the wording to indicate "only for legacy packages, we expect new packages to be in this format". I have to say that needing a patch for ''every'' upgrade of a pkg is annoying, sage -i should "just work". -- 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.
