Re: Bug#677474: Substvars for Build-Depends in the .dsc file
Joachim Breitner <firstname.lastname@example.org> writes:
> 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.
I think that the sources-subvars target must function without any
Build-Depends-(Indep) installed because otherwise:
- Checking out the source from RCS or downloading the source leaves the
source without full Build-Depends.
- Without Build-Depends the source can not be build.
- Without build the sources-subvars can't be generated.
and you are stuck in a vicious circle.
Similar for a debian/control target in debian/rules. Although there you
at least have the old Build-Depends to get you started.
Overall I'm not sure the substvars would be better than a debian/control