Yep ... That would be interesting01micko wrote::
Well the spup experiment then!
BTW I was looking through packages to cut from XOpup. Mostly apps that are highly unlikely to be used because of the hardware limitations.
First in my list is sane/xsane. The XO does not look like a machine to hook to a scanner. And that's a good 3MB compressed
Then, is the 9(!) cd/dvd apps and infrastructure. Again I do not see going around with the XO and a portable CD/DVD. About 0.5MB
Of cource the infamous 4 calculators could be cut down to by one
I also belive the gtkam/libgphoto can go. The XO is an unlikely machine to manipulate your camera and store the (5-12 megapixel) photos. That's 2+MB
Gnumeric can also go, but mtcell is really rudimentary as a spreadsheet app. I would rather have nothing instead. And that's 5+MB.
Finally is CUPS/printing. I personally like trees but I can see people wanting out of the box printing. So I'm not sure about this but that's another 3+MB...
These could be provided as one or multiple SFS/pets within the distributed tarball and people can decide what to use and when.
Frankly I do not see the XO as a "production machine". Is OK on the road and to work on something while at it, but hardly your (western adult) only machine.
The additional benefit of the trimming is that you release resources that may be used to run more kids/young-adults-oriented apps, in accordance with the XO target demographics. If not you just have a more responsive machine
Opinions?...
Edit: with these changes and the insertion of the 5MB wxcam+dependencies package so the XO-1[.5] camera works, the sfs is only 93MB. Not bad More important, it works