On 06/14/2012 11:04 AM, Joachim Breitner wrote: > Hi Bernd, > > Am Donnerstag, den 14.06.2012, 10:32 +0200 schrieb Bernd Zeimetz: >>> 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. > > I am aware of approaches using debian/control.in, but I was under the > impression that during the build, debian/control must not be changed and > hence this always requires manual interaction. If Updating > debian/control in the clean target, this is a large step in the right > direction.
Well, debian/control is not modified at build time anymore. It is created when *you* build the package before uploading it and should not be modified afterwards. > The only problem I see with this is that if the build dependencies can > only be calculated after a full build, building source and binaries > requires two builds (and a third one if debuild -tc is used). (Maybe > less if debian/rules tracks the dependency of debian/control on *.cabal, > but I’m not sure how reliable this is in the when packing and unpacking > the sources.) Not knowing the build-dependencies before building the packjage sounds... WRONG. Whatever you do to figure them out, please do it before uploadfing it and trying to do this on a buildd :\ -- 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/4fd9aa93.1000...@bzed.de
