For http://trac.sagemath.org/sage_trac/ticket/14505, I needed to libtoolize a rather old source (unchnaged for last 6 years), to get rid of a bunch of messy Makefiles etc. Apart from that, the change was in the layout of include/. I imported the upstream svn repo into git, and put it up on github. While it's perfectly possible to make a cumulative diff against the upstream source, and use it to create the spkg, I rather prefer to use the modified source on the git repo.
Another concern is the history of spkg-specific files; following libGAP's example I only provide a fake hg repo in the spkg, with the real history of changes documented on github. Any thoughts about this? Thanks, Dima -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
