I'm running vdr on a amd64 system and on a x86 system. On the amd64 the ebuild for gentoo-vdr-scripts totally respects "USE=nvram" only if I also set "USE=x86" or add: media-tv/gentoo-vdr-scripts x86 to the file /etc/portage/package.use That should not be required. Either nvram-wakup works on a platform or it doesn't. But I can not see a good reason why gentoo-vdr-scripts makes an additional decision about it. In detail: 1. "USE=nvram" is only used for dependencies in the ebuild script. 2. In the ebuild script the variable NVRAM is set depending up on "use x86", nothing else. For me, that is a bug. Reproducible: Always Steps to Reproduce: In /usr/portage/media-tv/gentoo-vdr-scripts/gentoo-vdr-scripts-0.3.8.ebuild you can find on line 36: >if use x86; then< Therefore "emerge gentoo-vdr-scripts" on a non x86 system will reproduce the bug.
So open another bug, get sys-power/nvram-wakeup tested and keyworded on amd64 and reopen once it's done. Until then, it stays as it is.
I have keyworded nvram-wakeup on amd64. Imo it should be handled by use.mask for ppc and any new archs added to gentoo-vdr-scripts and not to nvram-wakeup.
Can this bug be closed, as it seems Vapier did a use-flag cleaning on 2007/03/10. And since then it should work on amd64, but I cannot test it.
This Bug should be fixed. I will test it on the weekend, but I do not expect any surprises. Therefore I set it to fixed.
