On Tue, Feb 24, 2009 at 11:18:51PM -0500, Joey Hess wrote: > A few questions: > > * Earlier, you said you wanted to run waf in preference to > configure, but this looks to run it after?
That was based on the existing behaviour for Make.PL and setup.py, which both defer to autoconf should it exist. I work around it by doing "rm -f configure" in the clean target. > * Is there any good reason to add the check for waf before the check > for Build.PL? While it seems unlikely a package would include > both, this could in theory change how such a package builds and > probably break it. I stuck it directly below setup.py because they're both python thingies. I'm not really fussed if you would prefer it to go below. > * Suprised to see the Setup.hs patch included in this; similar > concerns with its ordering. They're separate patches, because I realized I forgot to file a separate wishlist bug for cabal (Setup.hs) support, and I couldn't be bothered working out how to cherry-pick patches in git-format-email. > * The one Setup.hs file that I tried (in hpodder) does not delete > Setup on 'Setup clean'. I need to talk to the other Debian-Haskell people about this stuff still. Right now I guess they're asleep (or defecting to Arch :-/). > * I'd really like to have the debian haskell people look over any > cabal/Setup/haskell stuff before putting it into debhelper, and > make sure we get it 100% right the first time. In particular [You're message got cut off here.] I have no problem getting Setup.hs stuff right before deploying it in unstable/testing; I just want to get started so that it's ready by the time Darcs (my package) transitions to cabal (scheduled for July). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
