On Thu, Oct 02, 2008 at 10:08:01AM -0700, Toshio Kuratomi wrote: > 4) make sure your package works with vanilla upstream versions of the > third party modules. It's tempting to fix things in your local copies > of modules. If at all possible don't. If that's not possible, make > sure upstream has incorporated the patch and make a note in the README > -- using a patched version of Foo-x.y project. The patch is in their > svn as of DATE. patch is located in myproject/foo-x.y/patches. Doing > this means that the distribution packager of your package can take your > patch to the packager of Foo and ask that the patch be incorporated there.
Mercurial's patch queues can be of great help for this. http://www.selenic.com/mercurial/wiki/index.cgi/MqExtension > development stuff. But I think that using eggs, workingenv, etc is a > fine solution for the development case. Someone told me about http://0install.net/ but I have not tested it and do not know how good/bad it is. -- Nicolas Chauvat logilab.fr - services en informatique scientifique et gestion de connaissances _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
