List Archive: gentoo-pms
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
>>>>> On Wed, 16 Dec 2009, Zac Medico wrote:
> Ciaran McCreesh wrote:
>> Unfortunately, Zac is doing otherwise, and experience shows that
>> what Zac does ends up being the final decision. You'll need to
>> either convince him to revert the other things he's put in EAPI 3
>> (which I think is just unpack changes, so far), or get the Council
>> to make him do so, or persuade the Council to change their minds on
>> what's in 3.
We don't need to do anything of the above. We abide by the council's
decision, because the council defines what goes into an EAPI and what
In any case, since .xz support will be in EAPI 4, it would be a
trivial change to move it to EAPI 3.
> The council doesn't have to "make" me do anything. The final EAPI 3
> will have exactly what the council wants and nothing more. I added
> xz unpack in EAPI 3_pre2 because I just assumed that everyone would
> agree on it. If the council wants to exclude xz unpack in the final
> EAPI 3, that's okay and I'll do as the council wishes.
Thank you for the clarification.
I guess it's an one-line change in Portage to include or not include
xz in EAPI 3?