Trent W. Buck wrote: > 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.
I think it's safest to always add new stuff the the end of these commands. Of course, that might mean the wrong stuff runs in some weird packages, but that's very unlikely and in such a package, one guess is probably as good as another -- as long as the guess is the same going forward. > > * 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.] [Don't think I really had anything important to add.] > 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). The existing haskell-devscripts stuff might be a good source for a first cut at getting it right. I am not sure though if debhelper itself can afford to encode quite as much haskell-specific knowledge as those commands do. At least, not until I use haskell a lot more. ;-) -- see shy jo
signature.asc
Description: Digital signature
