[gentoo-dev] EAPI 4 available, allowed in the main tree, ~testing ebuilds

2011-01-29 Thread Alex Alexander
Hello fellow devs, We're pleased to announce that EAPI 4 is now available and allowed in the main tree, in ~testing ebuilds :) New features in EAPI 4 include REQUIRED_USE, pkg_pretend, REPLACING_VERSIONS and REPLACED_BY_VERSION and various other interesting changes and fixes. To find out more ab

Re: [gentoo-dev] Glep 48 update (as nominated for next meeting)

2011-01-29 Thread Alec Warner
On Sat, Jan 29, 2011 at 5:07 AM, Fabian Groffen wrote: > On 28-01-2011 22:11:30 +0100, Tomáš Chvátal wrote: >> So draft we would like to have implemented as Glep update is this diff: >> http://dev.gentoo.org/~scarabeus/glep-0048.diff >> >> Please comment and help us improve the "english" of the wh

Re: [gentoo-dev] MULTI_ABI support addition to main tree portage

2011-01-29 Thread Pacho Ramos
El sáb, 29-01-2011 a las 19:56 +0100, Thomas Sachau escribió: > Am 29.01.2011 19:30, schrieb Pacho Ramos: > > El sáb, 29-01-2011 a las 13:10 -0500, Nathan Phillip Brink escribió: > >> On Sat, Jan 29, 2011 at 06:03:10PM +0100, Pacho Ramos wrote: > >>> > >>> Hello > >>> > >>> I would like to know wha

Re: [gentoo-dev] MULTI_ABI support addition to main tree portage

2011-01-29 Thread Thomas Sachau
Am 29.01.2011 19:30, schrieb Pacho Ramos: > El sáb, 29-01-2011 a las 13:10 -0500, Nathan Phillip Brink escribió: >> On Sat, Jan 29, 2011 at 06:03:10PM +0100, Pacho Ramos wrote: >>> >>> Hello >>> >>> I would like to know what is "blocking" this from landing main tree in >>> the "near" future, as I r

Re: [gentoo-dev] MULTI_ABI support addition to main tree portage

2011-01-29 Thread Pacho Ramos
El sáb, 29-01-2011 a las 13:10 -0500, Nathan Phillip Brink escribió: > On Sat, Jan 29, 2011 at 06:03:10PM +0100, Pacho Ramos wrote: > > > > Hello > > > > I would like to know what is "blocking" this from landing main tree in > > the "near" future, as I reviewed: > > > > http://www.mail-archive.c

Re: [gentoo-dev] MULTI_ABI support addition to main tree portage

2011-01-29 Thread Nathan Phillip Brink
On Sat, Jan 29, 2011 at 06:03:10PM +0100, Pacho Ramos wrote: > > Hello > > I would like to know what is "blocking" this from landing main tree in > the "near" future, as I reviewed: > > http://www.mail-archive.com/gentoo-dev@lists.gentoo.org/msg41737.html > > and looks like there wasn't major p

[gentoo-dev] Re: MULTI_ABI support addition to main tree portage

2011-01-29 Thread Nikos Chantziaras
On 01/29/2011 07:03 PM, Pacho Ramos wrote: I would like to know what is "blocking" this from landing main tree in the "near" future, as I reviewed: http://www.mail-archive.com/gentoo-dev@lists.gentoo.org/msg41737.html and looks like there wasn't major problems (at least commented in this thread

Re: [gentoo-dev] MULTI_ABI support addition to main tree portage

2011-01-29 Thread Pacho Ramos
El mié, 01-12-2010 a las 19:57 +0100, Thomas Sachau escribió: > Hi, > > i have already written about this some months ago and updated the code in > relation to the comments > especially from vapier. > > Basicly, it does now first set abi-specific vars (like CC, CFLAGS and others > (setup_abi_en

Re: [gentoo-dev] Glep 48 update (as nominated for next meeting)

2011-01-29 Thread Petteri Räty
On 01/29/2011 12:42 AM, Rich Freeman wrote: > > Finally, if Devrel, QA, and the Council have already talked this out > and agree that QA is in the best place to police technical commit > issues, then pipe this email to /dev/null... > The diff proposed in this thread has not yet been talked abou

Re: [gentoo-dev] Glep 48 update (as nominated for next meeting)

2011-01-29 Thread Fabian Groffen
On 28-01-2011 22:11:30 +0100, Tomáš Chvátal wrote: > So draft we would like to have implemented as Glep update is this diff: > http://dev.gentoo.org/~scarabeus/glep-0048.diff > > Please comment and help us improve the "english" of the whole document > so it gets accepted :) (:Nread http://dev.gen

Re: [gentoo-dev] Glep 48 update (as nominated for next meeting)

2011-01-29 Thread Roy Bamford
On 2011.01.29 05:20, Jeroen Roovers wrote: [snip] ... > and that whoever feels to be in place to > deal out QA (and I think this has gone wrong a few times recently) is > required to: > > 1) state and/or explain policy specifically where it is being not > adhered to; > 2) offer alternatives where