The Following User Says Thank You to jzencovich For This Useful Post: | ||
![]() |
2008-07-31
, 03:27
|
|
Posts: 549 |
Thanked: 502 times |
Joined on Feb 2008
@ Bowling Green Ohio (united states)
|
#3
|
The Following User Says Thank You to b-man For This Useful Post: | ||
As I understand it, scratchbox almost makes it as a separate VM.... meaning I have Linux on my computer, and then I have scratchbox within Linux (sort of like an embedded microOS ... a VM).
At first I thought it was more like a shell, so that any app available on my computer would also be available within scratchbox.
My problem comes in as I'm trying to port some software, as I'm compiling I'm running into dependency hell. Rather than try to compile from source any lib I need into scratchbox, I tried to use apt-get to build-dep (like 30 packages). But I keep failing for all sorts of different reasons (everything is configured right, sources.list is right... but i get weird nondescriptive errors "dependency can't be met, files are not in the repo"... things like that).
My question is about the inner workings of scratchbox, how does it get it's all its tools? And is there a way where I can make some sort of transparency that any tool/library that is on my computer will be available in scratchbox? I'm thinking perhaps symlinking, but I would rather learn more about the inner workings of how scratchbox works first. Or perhaps a way of creating my own rootstrap, mirrored off of my drive?
Any suggestions/enlightenment would be appreciated.
--Jon