I already know that people do also build their own packages, thanks. You do not need to "rewire" the debian/rules in order to build zeroc-ice binary-arch packages but AFAIK in your PowerPC you cannot currently build zeroc-ice binary-all packages, no matter what I do.
You do not need to issue an NMU if you find some binary-all packages that could be built in architectures other than i386. Report the bug and I will add them in the next release. The kludge will add another exception. Note that this is not a guarantee to be able to build binary-all but perhaps you could build binary/libzeroc-ice-java (?)
The zeroc-ice build dependencies are right to the best of my knowledge, but dpkg-buildpackage -B do not currently check them all. Target build must satisfy Build-Depends-Indep (cf. Debian Policy 7.7) but dpkg-buildpackage fail to enforce that for binary-arch builds. This is a feature rather than a bug in my opinion. This makes it possible to use target build while the transition path to build-arch is defined.
Simply stated, zeroc-ice is a package with lots of dependencies. I'll do my best to get most of it working in as much architectures as possible. But I won't remove features in some architectures just to homogeneize the behaviour of debian/rules. Therefore I'm eager to receive suggestions on how to make it *better* supported on any architecture. But I won't accept "DO NOT DO THAT" statements unless properly supported on the Debian Policy.
From: Wouter Verhelst [mailto:firstname.lastname@example.org]
Sent: Fri 15/08/2008 16:53
To: FRANCISCO MOYA FERNANDEZ
Subject: Re: Some autobuilders wait for build-indep dependencies
On Mon, Aug 11, 2008 at 11:29:53AM +0200, Francisco Moya wrote:
> I've uploaded a new version of zeroc-ice packages which essentially
> falls back to target build-arch whenever the autobuilder tries the build
> target on architectures other than i386. I hope the Build-Options
> control field or a similar approach will enter the Debian policy soon so
> that I can remove the kludge.
DO NOT DO THAT.
Building a package does not only happen on your own system or on buildd
hosts; it also happens on end-user hosts, or on the machines of fellow
developers. I don't *want* to have to deal with an NMU where I first
have to rewire the entire debian/rules file before I can build a decent
package on my powerpc-based laptop, thank you.
It's unfortunate that build-arch currently isn't really implemented, but
that's what currently the state is, so you'll have to go with it. Make
sure everything you need for both "clean", "build", and "binary-arch" is
installed for your build, and upload that. Please.
For reference, sbuild (the building part of buildd) currently uses
"dpkg-buildpackage -B" as the job that does the actual building. You're
welcome to patch dpkg so that that will call build-arch, but until
<Lo-lan-do> Home is where you have to wash the dishes.
-- #debian-devel, Freenode, 2004-09-22