genkernel always rebuilds busybox. Is this necessary? If not, we should store the prebuild busybox binaries somewhere and save us some time when running genkernel again. Reproducible: Always Steps to Reproduce: 1. run genkernel 2. rerun genkernel 3. rerun genk... (you name it[tm]) Actual Results: 1. busybox gets build 2. busybox gets build 3. busyb... (you name it[tm]) Expected Results: 1. busybox gets build 2. genkernel uses a cached build of busybox (yay!) 3. genkernel uses a cach... (you name it[tm]) Skipping as irrelevant for this bug.
Is there any way that we could use the existing busybox ebuild for this task?
We could add an internal "genkernel" use flag. If set, the "sed -e 's:<funnythings>:<evenfunnierthings>:'" stuff in genkernel could be done within the ebuild. Besides that, we would have to hack src_install() to install elsewhere. Finally, genkernel would have to emerge -b to build a package. If it doesn't hurt busybox, we might also incorporate the sed stuff into the normal busybox-<younameit>.ebuild and make genkernel RDEPEND on busybox. Then, we'd only have to copy over files. I'm not quite sure if this makes things really easier...
busybox is only built first time, then that binary is used for next builds in http://www.gentoo.org/~livewire/genkernel-beta.tar.bz2
