IMHO that should be the aim, but we shouldn't try to enforce it. Really they are bandaids for cases where upstream does something unreasonable. I see the spkg-src script more as documentation (its the log of commands needed on the current tarball) than something that can be run unattended on every new upstream release.
On Thursday, October 9, 2014 11:28:02 AM UTC+1, Jeroen Demeyer wrote: > > I have noticed that, for most of the spkg-src scripts, it is not > documented at all *how* they should be used. Also the developer > documentation at > http://www.sagemath.org/doc/developer/packaging.html#modified-tarballs > doesn't say what exactly such a script should do. > > This is because these are mostly left-overs from the old spkg system. > > And many of those scripts start with "rm -rf src" which would be a bad > idea to run from $SAGE_ROOT. > > To clear this up, we should fix what such a script should do and how it > should be called. I think the script should work within a Sage shell > (and it should check that it's being called from a Sage shell) from any > working directory and the end result of such a script should always be a > tarball ready-to-use in $SAGE_DISTFILES. > > And perhaps we should put all the common "boilerplate" of such scripts > in one central place. > -- 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 sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
