hi christian,

thanks for turning my attention.
i understand the problem of rebuilding the binary-indep (all) packages
on any architecture.

do you mean, i should also split the build into build-arch and
build-indep, and activate each build-* from it's appropriate binary-*?

if not, all upstream makefiles would need to be made on every
architecture, but will be packaged only when the appropriate binary-*
will be invoked.

please clarify this issue, so i could fix the problem.

btw, the control and rules files are missing form the example you
provided below (i am using sarge on i386).

best regards,

alex


On Tue, 2005-05-17 at 21:16 +0200, Christian T. Steigies wrote:
> Package: postgis
> Version: 1.0.0-1
> Severity: normal
> 
> Your package builds binary all debs on the buildds, this is from the build 
> log:
> 
> dpkg-deb: building package `libpostgis1-pg74' in 
> `../libpostgis1-pg74_1.0.0-1_m68k.deb'.
> dpkg-deb: building package `libpostgis-doc' in 
> `../libpostgis-doc_1.0.0-1_all.deb'.
> dpkg-deb: building package `libpostgis-java' in 
> `../libpostgis-java_1.0.0-1_all.deb'.
> 
> Packages that build the docs in binary-arch (Bdale's description):
> 
> Some source packages build all of the binary packages in the binary-arch
> target of debian/rules, even though at least one binary package is
> architecture independent. That's wrong.
> 
> The practical impact is that autobuilder maintainers get to manually
> clean up the _all.deb packages every time your package is uploaded.
> [Also it can add considerably to the build time on slow arches,
> and it's another potential source of build failures.]
> 
> Please fix this when you get a chance.
> 
> Any architecture "all" binary packages should be built by the
> binary-indep target in debian/rules. If you're using debhelper,
> read about the -a and -i options, and if you have dh-make
> installed, a good example rules file is available in the
> /usr/share/debhelper/dh_make/debian directory.
> 
> Christian
> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to