On Friday, June 8, 2018 at 10:25:33 AM UTC+2, Jeroen Demeyer wrote: > > On 2018-06-08 07:47, Ralf Stephan wrote: > > It might be an idea to semi-automatize this, i.e., build a tool that > > takes a Sage version and creates forks of some packages A,B on github > > under sage/sage-A, sage/sage-B. > > Which problem would that solve? >
For Sage devs, that of creating and maintaining a fork of a package. I do not suggest that making a fork per se solves a problem that is not already solved by the patches that are applied. However, it seems from the discussion that packagers are skeptical of Sage's patches. -- 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.
