On Wed, 6 May 2009 14:42:46 +0200 Simon Richter <sjr@debian.org> wrote: > I just uploaded debian-xcontrol 0.0.4 to Debian sid. Thanks, Simon. > Apart from implementing more control fields so the transformation > tool can be used with more packages, I've added a few extra fields in > the xcontrol file: > > - "Optional": This package is not built by the regular build target. > There needs to be a policy how to build these packages, my suggestion > would be "build-<packagename>" and "binary-<packagename>" targets. > This allows e.g. toolchain packages to list the cross variants in the > xcontrol file so an xcontrol aware autobuilder can see them and > specifically request them to be built. This is per-binary, defaults > to "no". Useful for the CodeAudit and regular packages too. It will provide a way to encode things like libgconf-noldap-2-4 etc. I'll build that support into emdebian-tools. It will be fairly simple to pick up the field in debian/xcontrol and activate those targets. That will put some flesh on the bones of a draft Policy via the Wiki. > - "Bootstrap": This package is intended as an intermediate when > bootstrapping something. For example, one could have a > freestanding gcc package that is tagged "bootstrap" and have the libc > build-depend either on the hosted or the freestanding compiler. A > bootstrapping autobuilder would then try to find a path with as few > "bootstrap" packages as possible. "Bootstrap" implies "Optional". > This is per-binary, defaults to "no". Interesting. > - "Cross-Compiling": This package supports cross-compilation in the > build-arch/binary-arch targets. Can be set globally for the source > package and overridden in the binary package stanzas. Defaults to > "no". Every debian/xcontrol file created by patches for emdebian-tools will gain this support as part of the CodeAudit and those changes fed into the mass bug filing in the Debian packages. Skipping certain packages entirely is very useful but I'm not sure how to implement support for that. Unless the package itself cleanly supports not building that package, omitting it can cause build failures. It is useful for gcc (which is enough reason to implement it even if no other package can use it) because we already need to "opt-out" of certain package builds when doing the reverse-cross build. It will take longer to implement that part of it. emdebian-tools will probably "switch-on" packages that are "Optional" && "Cross-Compiling: yes". I've updated the EmdebianCodeAudit wiki page with the new direction. > Also, you can now use the Build-Depends* fields in binary package > entries, those for non-optional packages are merged into the source > section's list. The xdpkg-checkbuilddeps program can query whether > the build-deps for a given package are fulfilled. Thanks. -- Neil Williams ============= http://www.data-freedom.org/ http://www.linux.codehelp.co.uk/ http://e-mail.is-not-s.ms/
Attachment:
pgp72jbXoc3Cn.pgp
Description: PGP signature