On 11/02/2014 10:28, Mick wrote:
> On Monday 10 Feb 2014 13:27:00 Jesús J. Guerrero Botella wrote:
>> Well, I don't have any problem with using whatever is suggested upstream.
>> The thing with USE flags is that they can be set globally, and when an
>> ebuild has an USE flag to enable or disable a given feature you are
>> supposed to be able to use that, that is, unless the ebuild has an ewarn
>> about it or the USE is masked. I try to make use of the documentation when
>> available, however this time I neglected to do so, mostly because a hard
>> lock is not something that's usually documented and partly because, to
>> start with, I didn't even know where to start looking.
>
> I'm going from memory here but recall that when I tried to emerge efl portage
> warned me about having xcb set. So I unset it and off it went completing the
> emerge.
>From efl-1.8.5.ebuild (in part):
REQUIRED_USE="
X? ( !xcb )
"
USE="X xcb" is enabled by default in the desktop profile so you will get
that warning and are forced to disable one of them when emerging efl for
the first time. For other profiles USE="xcb" is usually off, so enabling
it produces the same error message.
Most folks would think long and hard before setting USE="-X".
Perhaps the enlightenment herd can add an elog to clarify that not only
must one choose between X|xcb, but that xcb is completely unsupported
upstream so YMMV, break, both halves, keep + kittens => eaten
--
Alan McKinnon
[email protected]
------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
enlightenment-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-users
