After looking some at hg queues, I have a few more comments about how to handle patching packages sources.
* HG queues help with the issues of maintaining patches against a changing upstream source, but it is still a pain and nontrivial. * Because of this, I think mercurial queues only make sense when you really need it - when there are multiple patches that are difficult to diff/patch by hand. But in these cases, it probably does make lots of sense, and these sources should probably be in the hg repo. Thankfully, the big packages (qt/enthought) are not heavily patched. * However, for the many spkgs that don't have patches applied, it seems crazy to put the package source into the hg repo. * There is still the issue that maintaining patches is a pain. It seems like there are two broad categories of paches: 1) patches that simply fix a bug in the original source 2) patches that actually provide new functionality for sage or allow the package to be installed in the sage context. In the first case, I think we really need to try hard to make sure those patches get back upstream to the original package maintainers. I know of multiple spkgs that have such patches that have never been contributed upstream. Not doing this makes the spkgs more difficult to maintain (because there are more patches) and prevents to upstream projects from benefiting from our work. Brian On 5/31/07, Fernando Perez <[EMAIL PROTECTED]> wrote: > > On 5/31/07, Brian Granger <[EMAIL PROTECTED]> wrote: > > > source. This doesn't answer the question of how to maintain those > > patches, that don't get sent back upstream. This definitely needs to > > be addressed. > > If I understand correctly, that's what mercurial queues are for: > > http://hgbook.red-bean.com/hgbookch12.html > > Cheers, > > f > > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
