On 12-06-14 at 11:13am, Joachim Breitner wrote: > Hi, > > Am Donnerstag, den 14.06.2012, 11:10 +0200 schrieb Bernd Zeimetz: > > > 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 :\ > > that’s not what I am saying I would (let my mycomputer) figure them > out before uploading, as they would appear in the .dsc file. I was > assuming the buildds use the information in the .dsc files to install > the build dependencies, but if I read Julien’s mail correctly, this is > not the case, so my approach would indeed fail. Maybe buildds ignore debian/control and instead trust .dsc for needed build-dependencies, but if so that's an implementation detail. Debian Policy describes that if any build-dependencies are declared in debian/control they must be complete. So as I understand it, your suggested change need (at least) a change of Debian Policy. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
Attachment:
signature.asc
Description: Digital signature