View Single Post
Posts: 805 | Thanked: 1,605 times | Joined on Feb 2010 @ Gdynia, Poland
#9
Originally Posted by Mentalist Traceur View Post
(Although I think you could put a chroot inside /opt/something and then permanently add that chroot's (s)bin directories to your path, then make install from within the chroot. Since the binaries inside the chroot will still be N900's-Maemo5-runnable, assuming you set up the chroot correctly. Although I'm not sure if I understand chroots right, but I think it should be possible to have a chroot that's just part of the filesystem it's in, rather than a seperate file...? [so all the stuff inside it is visible/runnable even when the chroot isn't running])
That was exactly my idea You don't need chroot into the image file, you may mount it in the same way EMMC and SD cards are mounted on system (just 1 command in xterm or in some script if someone wants it automated) and the file is mounted and can be accesed under some path of filesystem. For example one may want to mount file /home/user/MyDocs/nicebigimage.ext3 under /opt/awesomefs and then just update patch so binaries are search in /opt/awesomefs/bin and libraries in /opt/awesomefs/lib (just example paths). Honestly, if I were to package some bigger software for N900 (bigger=above 1GB), I would even create a package that way. That just makes it impossible to connect N900 to computer as external usb drive while running programs from this mounted image. If someone would have enough patience and would really need it, he could write even some scripts and connect them to dbus signals and unmount or mount this virtual fs accordingly.

It's late in here (and end of week), so I hope I wrote my thoughts in understandable way.
 

The Following User Says Thank You to misiak For This Useful Post: