Hi, > I would like to see more flexibility in dpkg-source as to where the > effective build depends come from. My use case are (as you might guess) > Haskell packages. If you look at > http://ftp.de.debian.org/debian/pool/main/h/haskell-yesod/haskell-yesod_1.0.1.6-1.dsc > you see it has a very long list of build dependencies. If you’d compare > that to > http://hackage.haskell.org/packages/archive/yesod/1.0.1.6/yesod.cabal > you’d see that the process of creating the build dependencies is a > mostly mechanical process and doing that manually is a waste of human > developer time and a source for mistakes (which lead to FTBFSes and > hence more waste in buildd and buildd admin time).
Other peopel solve this by having a debian/control.in file and having - a debian/control target in debian/rules - having the clean target depend on debian/control. I don't think that your case is special enough to add yet an extra option to dpkg-source. I have two packages where I'm changing much more than the build-dependencies automatically, for example. Cheers, Bernd -- Bernd Zeimetz Debian GNU/Linux Developer http://bzed.de http://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fd9a18c.6070...@bzed.de
