To be completely clear, two additional questions: On Thursday, January 23, 2014 10:57:29 AM UTC+1, John Cremona wrote: > > Here is how I have interprested these questions for the packages I am > involved in maintining: > > * package-version.txt, should it only be updated when the tarball > changes? > > this is what > > http://www.sagemath.org/doc/developer/packaging.html#package-versioning > > suggests, not what the discussion between Jeroen and I at > > http://trac.sagemath.org/ticket/15123#comment:32 did. > > Yes. It's a label for the upstream version. Local changes to what we > do with the tarball are tracked by git anyway. > > Is this enough to trigger a package rebuild if you for example add a patch?
> > * history in SPKG.txt, > > http://www.sagemath.org/doc/developer/packaging.html#the-spkg-txt-filesays > > no history anymore, so should we just get rid of the old history when > > updating? as remarked http://trac.sagemath.org/ticket/15123#comment:24it is > > still available in the hg/git history (and I'd better have no info kept > in > > SPKG.txt than just old info). > > Correct: the new SPKG.txt does not contain its own update history. > > So you actually removed all the old info stored there? Best, JP -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at http://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/groups/opt_out.
