Talk:Test Openmoko Emulation with chroot image
(JoSch) It took me several hours to run the openmoko makefile on my AMD Athlon 64 X2 3800+ so it would be nice to have the complete environment without having to compile the whole stuff BUT
- wouldn'd it also costs hours to unpack such a big archive with so much files?
- <kriss> It's only one image file and it took me 20 min on to decompress (1 core Athlon 3500+). - But I could also provide a .gz file and one without temporary files...
- where should such a big file be hosted permanently with the necessary download speed and transfer volume?
- <kriss> I can host it at my university for free and at 100 Mbit/s.
- isn't it 'unfair' to choose just one distribution for the chroot environment instead of supplying a guide how everyone could set up their own?
- so wouldn't it be cleaner to just supply a compressed version of the openmoko build environment and the distribution specific files are suppplied by the user?
- isn't it hard to maintain such a giant file over the time and support errors the users have with it?
- wouldn't everyone still use the makefile because the files downloaded by it should generally be newer than the files in your archive?
- <kriss> Yes, Its just for testing. - Just that I have it laying around here, and people want it. - I guess I could even do a "make update-makefile && make update setup openmoko-devel-image" on the image from time to time...
Peer-peer networks suit this sort of distribution well. Unpacking takes minutes generally - even slow disks can create files at some 20/s.
Unfair - of course not.
You are saving users time and effort and hastle. Patches can be simply delivered as overlay archives which are extracted over the filesystem. --Speedevil 11:14, 16 July 2007 (CEST)