$ sudo emerge --config =postgresql-8.1.5-r1 Configuring pkg... * Creating the data directory ... * Initializing the database ... * QA Notice: USE Flag 'kernel_linux' not in IUSE for dev-db/postgresql-8.1.5-r1 The files belonging to this database system will be owned by user "postgres". This user must also own the server process. The database cluster will be initialized with locales [...]
Eh, you know... This is 200% pointless cruft in IUSE; portage should just STFU about USE_EXPAND_HIDDEN stuff, there's nothing for users to see or change there. Plus adding this even triggers --newuse which is completely inexplicable to users because the flag is invisible; argh.
Er... The whole point of USE_EXPAND_HIDDEN, as I understand it, is so that the special flags can be stuck in IUSE without cluttering emerge -pv. If these flags are kept out, USE_EXPAND_HIDDEN is pointless. If you're only asking for emerge --newuse to ignore USE_EXPAND_HIDDEN flags, then I don't necessarily disagree, but wouldn't it be better to do that in a separate bug?
Or perhaps make this check ignore certain USE_EXPAND variables?
(In reply to comment #3) > Or perhaps make this check ignore certain USE_EXPAND variables? OTOH, why not put certain flags into IUSE automatically (implicitly) in cases where it makes sense? That would prevent the QA warning from being triggered in the first place. It already ignores ARCH. We can do the same for other flags that can be considered implicitly within IUSE. The most obvious ones are already listed in USE_EXPAND_HIDDEN in make.defaults of the base profile: USERLAND, KERNEL, and ELIBC.
Oh well, possible solutions... 1/ Fix Bug 133327 or some variation of what's mentioned in Comment #4 2/ Or just make portage shut up about USE_EXPAND_HIDDEN (sorta duplicate of Bug 70648, just restricted to this one special case... :) plus definitely don't let this get triggered by --newuse; it is really confusing and will make lots of users annoyed if 1/ is chosen.
*** Bug 184983 has been marked as a duplicate of this bug. ***
Well, this has nothing to do with postgresql stuff; re-assigning to portage. Find a solution that doesn't confuse the hell out of users (Bug 184983 and alikes).
We will solve this bug by adding kernel_linux to IUSE together with other bugfixes and a revision bump.
Sorry for the bug-spam.
dupe it of Bug 70648 ... there's nothing to change in the postgres ebuilds
Fixed in dev-db/postgresq-{base,server}
