Bug#666726: debian-policy: Clarify if empty control fields are ollowed or not
On Sun, 23 Nov 2014, Jakub Wilk wrote:
> * Henrique de Moraes Holschuh <firstname.lastname@example.org>, 2014-11-23, 18:49:
> >>This bug is mostly to document a check in dak. Are you
> >>suggesting the check is looking at the debian/control file and
> >>reject source packages with empty fields?
> >That would be broken beyond belief! debian/control might not even
> >*exist* after source package unpack when it is autogenerated
> >during the build.
> Not quite. dpkg-buildpackage checks for existence of debian/control
> before running debian/rules. So if the source package doesn't ship
> the file, it will FTBFS.
Hmm, I stand corrected. And I should say I rather prefer a world where
debian/control is there when the source is unpacked, so I am happy to have
been wrong about this :-)
> Moreover, ftp-masters require that certain things in debian/control
> (Build-Depends, package list) do not change during package build:
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot