On Wed, Nov 18, 2015 at 10:23 AM, Brian Dolbec <dol...@gentoo.org> wrote:
> On Wed, 18 Nov 2015 12:02:15 +0100
> Alexis Ballier <aball...@gentoo.org> wrote:
>
>> On Wed, 18 Nov 2015 21:53:17 +1100
>> Michael Palimaka <kensing...@gentoo.org> wrote:
>>
>> > What do you think?
>>
>>
>> +1
>>
>> even if I sometimes use those cmake-utils_use*, they tend to confuse
>> me and find -DABCD=$(usex ...) much easier to understand for the
>> occasional user of cmake-utils.eclass.
>>
>
>
> Forgive me if I'm wrong, but I thought EAPI 6 specifications were
> finalized.
>
> Doesn't that mean this will have to wait for EAPI 7?
eclass API is not directly tied to EAPI/PMS. However,
cmake-utils.eclass has this:
case ${EAPI} in
2|3|4|5) : ;;
*) die "EAPI=${EAPI:-0} is not supported" ;;
esac
That means that its API is currently undefined when EAPI is set to 6;
the eclass will immediately die.
This is just a convenient opportunity to change the API of this eclass
without risking breakage of existing ebuilds.
