On 18.06.2007, at 17:21, Philipp Riegger wrote:
Ok, i seem to have mixed up the stages. portage_confdir is used in stage3 and livecd-stage1 target, of course, but not in livecd- stage2. Is there any specific reason, why it is not supported (like the documentation says)? What is the right way to set use- flags for genkernels callback function? boot/kernel/[boot/ kernel:x]/use? What does [boot/kernel:x] stand for?I got some info on that on IRC. Sorry for the noise, this is fixed now.
Ok, more noise from me. I was asked about how i fixed this for me and when i re-read my email, i figured out, that i don't know all the things i want to know:
The problem i had was due to a use-flag injected in livecd.conf in gnap, the line was more or less "boot/kernel/gentoo/use: esfq". I missed it when i grep'ed my conf dir before, probably some typing mistake in the regex.
So my USE-flag was injected this way, and it did not work disabling it using a portage_confdir, as i stated in the second email.
But: In livecd-stage2 there is the genkernel callback function, which is in my case a emerge call. I don't know how it is in general, but probably the same. And for this emerge call it might be quite handy to have package.mask and package.keywords. So, why was the desicion made to use boot/kernel/whatever/use instead of portage_confdir, which is much more flexible?
Again, what does the [boot/kernel:x] in the documentation stand for?
Thanks a lot,
Philipp
PGP.sig
Description: This is a digitally signed message part
