Hello,

I've been wondering for some time if it would be possible create 
pbuilder-like infrastructure on top of scratchbox2 (for building .debs).  
Namely, what I would like to have is tools (consisting of say squeeze + 
cross toolchain) and target (say armel).  I can setup these with 
debootstrap, no problem here.

However, problem starts with introduction of non-trivial Build-Depends 
(other than 'build-essential').  Having basic native/target environments 
I would like to automatically resolve and install dependencies.
devel's mode dpkg-checkbuilddeps wrapper is quite capable of handling pre-
setup environment, however I have hard time finding how to automatically 
decide which packages would be needed to be installed to tools, target or 
tools+target.

My investigation suggests that I would basically need to modify dpkg-
checkbuilddeps (because intelligence is already there) and:
 (1) download given missing package for an architecture (say - tools' 
amd64), hmm... maybe use apt-file instead of downloading package in this 
step
 (2) check what files are included in package (and/or use include/exclude 
lists) and decide if this package is installable on tools, target or both
 (3) install package(s) where it belongs
 (4) repeat this for every package in build-depends.

However... I guess even that wouldn't be sufficient as I would need to 
solve dependencies manually.  That looks like a mess for me.  Huge mess.

Maybe I'm missing something?  Something obvious?  Hints, suggestions, 
tools-from-under-the-carpet - more than welcome. ;)

Karol

_______________________________________________
Scratchbox-devel mailing list
[email protected]
http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-devel

Reply via email to