Archive-wide build-arch and build-indep support
This release goal is about getting archive-wide support for the 2 recommended targets "build-arch" and "build-indep". The primary focus are packages that would benefit from these targets (i.e. building both arch:all and non-arch:all packages).
- Goal is not approved.
This is related to 629385.
All packages missing the build-arch or/and the build-indep targets should be found by lintian via the debian-rules-missing-recommended-target
- Detailed stats are available on lintian.d.o:/srv/lintian.debian.org/history/tags/debian-rules-missing-recommended-target.dat
A list of orphaned packages affected by this release goal and which build more than one binary package is available here: http://people.debian.org/~codehelp/orphaned-list.txt - always check current status of orphaned packages, some in this list may already have RM bugs filed. qt-x11-free is ignored in this list. See qt3-x11-freeRemoval
Same kind of list but for the larger reduced set: http://people.debian.org/~codehelp/reduced-set.txt - the test was run on amd64 without non-free sources, some packages are missing descriptions for this reason.
How to help
- Sign up as a volunteer (or advocate).
- Fix packages.
- If filing bugs, please use:
How to fix a package
- A package without Build-Depends-Indep is straight forward.
The lintian tag description should cover most cases.
Packages with Build-Depends-Indep requires a lot more care.
- buildds will not install Build-Depends-Indep.
- The build most likely done with "build" followed by "binary-arch". This makes them very hard to fix.
- Merging Build-Depends-Indep into Build-Depends may be okay if the B-D-I fetches a "small" set of packages.
But do not blindly assume a few packages translate to a small set of packages
- i.e. doxygen-latex is worth 190MB extra packages (on i386).
Niels Thykier <firstname.lastname@example.org>
Jakub Wilk <email@example.com>
Bernhard R. Link <firstname.lastname@example.org>
George Danchev <email@example.com>
Neil Williams <firstname.lastname@example.org>