[Scratchbox-users] Problems with tools in debian devkit. Can some/all tools be replaced?

[Riku Voipio]

On Fri, Jan 05, 2007 at 06:12:51PM -0500, Jim Heck wrote:
-snip-
> dh_consoledata -i
> /scratchbox/tools/bin/sh: line 1: 
> /usr/share/debhelper/dh-consoledata/config.in: No such file or directory
> dh_consoledata: command returned error code
> make: *** [binary-indep] Error 1
-snip- 
> The file /usr/share/debhelper/dh-consoledata/config.in truly does not 
> work.  Unfortunately, pbuilder-satisfydepends decided not to install 
> that package, and use the Scratchbox provided version instead (which is 
> missing the needed file).
-snip-
> So, in a crocodile build scenario, is it possible to have 
> pbuilder-satisfydepends defer to installing the package if it is built 
> instead of using the Scratchbox version?  Would this even work (I can 
> imagine installing the second version in addition to the Scratchbox one 
> could cause problems)?  I'm running into several problems more like the 
> first where the tool has changed and the modern Sarge makefiles employ 
> the wrong syntax.
-snip-

You are attempting to work around a issue: dh-consoledata is
broken in debian devkit. Either you can fix console-data build rule,
or you can just remove /scratchbox/devkits/debian/deb_list/console-common.

In general current system should match sarge, and if it doesn't it's 
a bug.

> environment variables in addition to populating tools.  Really what I am 
> looking for is to have built as much from Sarge source as possible, so 
> I'm depending as little as possible on specific versions of tools from 
> the devkit.
 
> I've read a bit about Scratchbox 2, and it sounds somewhat more like 
> what I'm trying to do here, but I haven't found enough to really 
> understand if it is ready to be fully used, and if so, what the ins and 
> outs are vs the older Scratchbox.

This is exactly something that scratchbox2 [1] should make possible.
Or actually better, you don't need to _avoid_ host tools in order
to select your preferred host tools versions. You can just install
the version you want. Currently sbox2 can build applications 
(./configure ; make ; make install) , however nobody has written
enough remapping rules to build .deb:s (should be easy) or install
target libraries with apt-get (a more tricky problem). I suggest you
take a closer look, sbox2 is much smaller and easier to grasp than
1.x series. The only hard part is the remapping engine.

[1] http://rahina.org/sb2/