These drivers will never be able to go stable, as it is currently designed. For one, it requires a portage FEATURE, yet does not have the portage version in DEPEND. Second, there is no way to determine the profile being used, so multilib may not be enabled on the user's machine. This ebuild needs to use the multilib USE flag, as there are profiles that do not force multilib, and there will be profiles that do not force multilib for the forseeable future.
eradicator any comment about that issue?
Chris, can you please be a little more specific here? 1) It doesn't require any portage feature. In fact the comment about a portage FEATURE is a reminder to cleanup the code and DEPEND on a new version of portage when a feature is introduced. 2) It doesn't force multilib.
closing