Denis Dupeyron wrote:
> 2. EAPI3 status (10 minutes)
> Can we have an ETA? Even a vague one would help.
I guess about 3 months or so, but it's hard to say. See tracker bug
here as usual: http://bugs.gentoo.org/show_bug.cgi?id=273620.
While we're on this topic, I think we may want to consider dr
Ciaran McCreesh wrote:
> On Thu, 19 Nov 2009 17:14:20 -0700
> Denis Dupeyron wrote:
>> On Thu, Nov 19, 2009 at 3:12 PM, Ciaran McCreesh
>> wrote:
>>> I honestly don't think we should be going anywhere with this until
>>> Portage is using a mechanism that guarantees correct sub-second
>>> resoluti
Ciaran McCreesh wrote:
> On Wed, 4 Nov 2009 16:07:30 +0100
> Ulrich Mueller wrote:
>> Obviously we cannot guarantee anything below the seconds level because
>> of limitations in the underlying filesystems or software (e.g., tar
>> for binpkgs). But is there a reason for limiting it further, i.e. n
Petteri Räty wrote:
> 2. Progress report of EAPI 3 implementation
I plan to work on it in the near future. I was putting it off until
the after 2.1.7 release was out, but that's done now. So, you can
expect to see some progress soon. There's a tracker bug here:
http://bugs.gentoo.org/show_bug.c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Petteri Räty wrote:
> Donnie Berkholz wrote:
>> Furthermore, why do I need to prod people for an update? When you commit
>> to a date, you should be minimally sending out *something* on that date
>> to let us know what is blocking progress. I don't e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lukasz Damentko wrote:
> I'd like to nominate zmedico, robbat2, tsunam and musikc. Why? Their
> role in the project is so significant that they should get a chance to
> run for a position on the Council.
Thank you for the nomination. However, I will d
