Marius Vollmer wrote: > There are two kinds of borders: one kind isolates OSs from each other; > this could be done with some virtualization tool like xen, uml, or > maybe chroot. The other kind isolates different architectures within > the same distribution; this is what SB2 does. > There has been some thinking about this dilemma, and we have pretty much decided that we will not implement anything that does the first kind of isolation in sb2. A separate tool can be created for that purpose.
Lets try to keep sb simple this time :) > In order for me to use SB2 and still retain control over my host OS, I > would have to install the OS that SB2 wants as its host inside a > virtual machine. That's not a problem, of course. I think I found my > weekend project... > That is not that different than what Debian/Ubuntu developers already do. Their host OS is whatever it is (etch/testing/sid or dapper/gutsy or whatever), with whatever crap and extra hacks installed. When building packages to distro, a clean chroot of target distro or pbuilder is used. > So, in the end, I think it's actually all quite simple: we make a OS > that runs on real x86 hardware, inside Xen on x86 and on a Internet > Tablet arm device and can be used both as a development environment as > well as the basis for IT OS. That OS includes sb2 which is used to > 'cross-compile' software from i386 to armel. > The *main* point here needs to be that all development tools inside the X86 development system need to unmodified packages from some mainstream distro. Else we end up maintaining a similar soup of patched and hacked packages that nobody dares to upgrade. _______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
