On 9/30/13 1:31 AM, hero...@gentoo.org wrote:
> Having a unstable eclass as toolchain-r1.eclass in tree might not be a
> good idea compared to an overlay though.
If that's the case, it should be pretty straightforward to create an
overlay with that eclass, either under toolchain-r1 or just
toolcha
"Rick \"Zero_Chaos\" Farina" writes:
> While I'm not nearly good enough to detail how this should happen
> exactly, please, may I beg, do an eclass revision for this.
There is an r1 candidate as Paweł initiated (bug 474358)
> The fact that this hasn't been done clearly implies it is a lot of
On 29/09/13 04:12, hero...@gentoo.org wrote:
> It's just a starting point, though. I still don't have a clear plan yet.
>
> After reading carefully the thread Ulrich pointed out, it seems that
> refactoring ebuild/eclass is invevitable, which calls for an overlay to
> carry it on.
That would be m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/28/2013 10:12 PM, hero...@gentoo.org wrote:
> "Rick \"Zero_Chaos\" Farina" writes:
>
>> On 09/28/2013 03:00 AM, Ulrich Mueller wrote:
On Sat, 28 Sep 2013, heroxbd wrote:
>>>
I am revisiting this topic based on previous discussion
"Rick \"Zero_Chaos\" Farina" writes:
> On 09/28/2013 03:00 AM, Ulrich Mueller wrote:
>>> On Sat, 28 Sep 2013, heroxbd wrote:
>>
>>> I am revisiting this topic based on previous discussions[1,2,3].
>>
>>> There seems to be a constant need for toolchain with a new EAPI. The
>>> only block is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/28/2013 03:00 AM, Ulrich Mueller wrote:
>> On Sat, 28 Sep 2013, heroxbd wrote:
>
>> I am revisiting this topic based on previous discussions[1,2,3].
>
>> There seems to be a constant need for toolchain with a new EAPI. The
>> only block is
> On Sat, 28 Sep 2013, heroxbd wrote:
> I am revisiting this topic based on previous discussions[1,2,3].
> There seems to be a constant need for toolchain with a new EAPI. The
> only block is "how can we upgrade from an ancient system?", "don't
> bump or the upgrade path will be break". Let'
Dear Fellows,
I am revisiting this topic based on previous discussions[1,2,3].
There seems to be a constant need for toolchain with a new EAPI. The
only block is "how can we upgrade from an ancient system?", "don't bump
or the upgrade path will be break". Let's figure out a solid upgrade
path con
