On Wed, 2007-06-20 at 01:06 +0300, Philipp Riegger wrote: > 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?
Release Engineering *never* uses portage_confdir for our official builds and never will. Everything must reside in the spec file itself. The only reason that portage_confdir exists is for you guys to allow you to hack up your own builds in a manner that would be totally unacceptable, by Release Engineering standards. The best/most tested method for changing USE is boot/kernel/$x/use in your spec file. > Again, what does the [boot/kernel:x] in the documentation stand for? Huh? -- Chris Gianelloni Release Engineering Strategic Lead Alpha/AMD64/x86 Architecture Teams Games Developer/Council Member/Foundation Trustee Gentoo Foundation
signature.asc
Description: This is a digitally signed message part
