REQUIRED_USE in EAPI 4
As you probably have noticed, the Council has frozen the feature set
for EAPI 4 in its November meeting , based on the current status of
implementation in portage. These features include the REQUIRED_USE
variable that will allow to specify constraints on USE flags possible
for an ebuild, as proposed by ferringb .
A first wording for the REQUIRED_USE specification in PMS is available
in bug 347353 . As was pointed out in that bug, the current
treatment of violated USE flag constraints isn't optimal. Portage
basically would output "REQUIRED_USE violated", together with the
variable's value and the package name. Such a message might not be
very helpful for the user. And presumably there is no universal
algorithm that can output a reasonable suggestion based on USE and
Since generally the ebuild maintainer will know best what should be
suggested to the user, a new function "pkg_required_use" has been
proposed by zmedico. It would be triggered only in the case that
REQUIRED_USE is not fulfilled, and it would output a message for the
user, similar to pkg_nofetch for fetch-restricted packages.
|All times are GMT. The time now is 01:12 AM.|
VBulletin, Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.