On Thu, 2012-12-06 at 13:01 +0100, Bastian Blank wrote: > On Thu, Dec 06, 2012 at 02:16:16AM +0000, Wookey wrote: > > In order to bootstrap a new architecture, a cross-toolchain must be > > built. A suitable linux-libc-dev_$arch package is needed for this. In > > order to make this (and cross-toolchain builds in general) > > automatable, the packaging needs to be able to build just this package. > > You can always produce a proper binary package without patches. A > package must not produce different output just because. It needs a new > changelog entry and version. Please use gencontrol to remove the other > binary packages in this case. > > > The attached patch provides this functionality. > > It makes the control file invalid.
The binary packages and control files for intermediate stages do *not* need to comply with normal policy. They *do* need to be buildable in a standardised way (so no package-specific stuff like gencontrol.py). Ben. -- Ben Hutchings Computers are not intelligent. They only think they are.
signature.asc
Description: This is a digitally signed message part
