On 05/28/2010 03:29 PM, Lennart Sorensen wrote: > uboot pretty much #defines everything for a given system and compiles > based on that, so you would need to just about make a seperate package > for every target system you want to make a uboot for. That could be a > lot of packages. not to say it shouldn't happen, I am just not sure if > it would happen. Would you want to rebuild 200 target packages if you > make a change to the source code which only affects 1 or 2 targets? > That is after all what a package would tend to do. Thanks for the perspective, Lennart. Currently, u-boot isn't in debian at all, yet i need it to boot my guruplug. so i'd like to see that situation improve, but i'm not sure the best way to do it. I see a few possibilities: * package the u-boot sources and make a single u-boot-installer image that makes it easy for debian folks to build their own flavor of u-boot. in that case, maybe a "u-boot-install" utility (by analogy with grub-install?) would actually compile the code as needed and then move it into place. * package u-boot, but only add specific binary packages as requested. that is: one source package, and initially maybe only 1 binary package (for the guruplug, since i'm the one requesting ;) ). add more packages as people want them? * Make a separate u-boot source package following each of the main architecture custodians' "forks", and have each source package create separate binary packages for the various sub-arch targets. What do folks think would be reasonable? --dkg
Attachment:
signature.asc
Description: OpenPGP digital signature