On Wed, Jun 25, 2008 at 23:57, Sandro Tosi <[EMAIL PROTECTED]> wrote: > On Wed, Jun 25, 2008 at 23:39, Chris Lawrence <[EMAIL PROTECTED]> wrote: >> On Wed, Jun 25, 2008 at 4:32 PM, Sandro Tosi <[EMAIL PROTECTED]> wrote: >>> Well, on which version to merge, I think you should reach a consensus >>> with Chris. >> >> Probably the easiest way to go about this is to merge Ben's work >> around the end of the week and release 3.42 based on that. We can >> then decide whether proper modularization (the python-reportbug >> package, based on my work) is appropriate for lenny or if we should >> wait for the next testing cycle. My gut feeling is that we can >> probably get python-reportbug into lenny without any issues and I >> think that would be better in the long run. > > well, so why wait? I think if that's the way to go, then Ben can merge > asap (I got no commit pending on my side), so we can work on that > version, then Chris you have more time to work on your tree to be > merged after 3.42.
mh, I just gave a look to Ben's "branch": do we really need an additional level (reportbuglib) into /usr/share/reportbug/ ? I don't know how Chris' tree looks like, but having (-> means installed into) <svn trunk>/bin/reportbug -> /usr/bin/reportbug <svn trunk>/reportbug/<files>.py -> /usr/share/reportbug/ so that we can import reportbug (the trick can be adding /usr/share to sys.path and leaving reportbug/ in it, as of now, I think) it seems to me a "cleaner" solution. Sandro -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi _______________________________________________ Reportbug-maint mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/reportbug-maint
