The latest baselayout adds a bootchart feature: # Set to "yes" if you want to benchmark system boot with bootchart. # You'll need to emerge the apps-benchmark/bootchart package for this to work. RC_BOOTCHART="no" However, apps-benchmark/bootchart is not in portage. Additionally, the portage category is app-benchmarks not apps-benchmark - I assume this is a type and it's going to go here and not create a new redundent category.
*** This bug has been marked as a duplicate of 74425 ***
I'm sorry but I don't feel simply closing this bug and linking to the bootchart bug is an acceptable solution. Bootchart may be going in to portage Soon(TM) but the fact is that it's not in portage now, yet a baselayout configuration file is telling users it is. I feel this could be confusing to many users. Surely the correct resolution is to change the entry in /etc/conf.d/rc, at the very least adding a short comment along the lines of: # This package is not yet in portage at the time of writing, but is going in soon. # Please see https://bugs.gentoo.org/show_bug.cgi?id=74425 for details. I know it's pedantic, but I think it's just plain wrong to tell people a package is in portage when it isn't and doesn't appear to have any timeframe (other than "when this last issue is resolved") either. You also haven't made any comment at all on the (possible) typo I mentioned.
(In reply to comment #2) I concur completely. Telling the user to emerge an app that is not yet in portage to support a stable baselayout -- a significant QA overlook. (IMHO, less-than-adequate QA was performed on baseylayout-1.12.4 before marking it stable.) This bug depends on bug 74425, but I cannot mark it as such ;-) .
Boot chart is in portage now
As far as I can see the name of the environment variable in /etc/conf.d/rc is wrong. I have a default entry RC_BOOTCHART="no" but the message from apps-benchmark/bootchart ist to set RC_USE_BOOTCHART="yes".
