Hi,
On Thu, 07 Jun 2012, P. J. McDermott wrote:
> Generalization
> ==============
[...]
> Rather than modifying a lot of dpkg code to handle field "patterns" or
> the like, I propose a simple dynamic definition of "Build-Depends-
> StageN" and "Build-Depends-Indep-StageN" hash elements in %FIELDS:
>
> 'Build-Depends-Stage'.$buildstage => {
> allowed => ALL_SRC,
> dependency => 'normal',
> dep_order => 3,
> },
>
> Then $buildstage could be defined by parsing DEB_BUILD_OPTIONS in
> Dpkg::Control::Fields.
This is not OK. It means that those fields would be basically unknown
when you're not doing a staged build. Yet they are always present
in debian/control (and probably the .dsc) and thus they need to exist
in that hash to avoid warnings, and to be able to output them in the
correct order, etc.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Get the Debian Administrator's Handbook:
→ http://debian-handbook.info/get/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
