Talk:Test Openmoko Emulation with chroot image
From Openmoko
m (comment) |
|||
Line 7: | Line 7: | ||
# isn't it hard to maintain such a giant file over the time and support errors the users have with it? | # 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? | # wouldn't everyone still use the makefile because the files downloaded by it should generally be newer than the files in your archive? | ||
+ | |||
+ | |||
+ | |||
+ | 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. | ||
+ | --[[User:Speedevil|Speedevil]] 11:14, 16 July 2007 (CEST) |
Revision as of 11:14, 16 July 2007
(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?
- where should such a big file be hosted permanently with the necessary download speed and transfer volume?
- 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?
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)