Hi, On Fri, Dec 02, 2016 at 10:59:48PM -0800, Ralf Stephan wrote: > Apologies. I had the impression that repackaging is frowned upon for > security reasons. However, just removing files can be automated, either by > the original author or the Sage release manager, so there is room for > improvement.
I also like the fact that we use untouched upstream tarball. I was just pointing that it was not related to making a package standard (look, e.g. at rubiks bundle). It would be good to transform the 'sed' part of giac's spkg-src into a real patch. > So, for making giac standard package, we are practically waiting for the > release manager to just do it, right? I guess the usual procedure is to ask for consensus on sage-devel, then create a ticket that changes the 'type' file from 'optional' to 'standard', then indeed the release-manager will add the tarball to Sage source tarball. Ciao, Thierry -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
