On Sat, Oct 15, 2011 at 03:54, Mike Gilbert flop...@gentoo.org wrote:
That would be an ok approach from my perspective: We could just change
line 14 of python.eclass and let package maintainers report breakage as
they increment EAPI. I am confident that nothing EAPI = 3 would break.
Is anyone
On Fri, Oct 14, 2011 at 9:54 PM, Mike Gilbert flop...@gentoo.org wrote:
On 10/14/2011 09:11 PM, Paweł Hajdan, Jr. wrote:
On 10/14/11 5:38 PM, Alec Warner wrote:
I believe op's point is that there is no one to escalate the problem
to; certainly the council members are not going to do the work
On 10/15/11 2:42 AM, Dirkjan Ochtman wrote:
On Sat, Oct 15, 2011 at 03:54, Mike Gilbert flop...@gentoo.org wrote:
That would be an ok approach from my perspective: We could just change
line 14 of python.eclass and let package maintainers report breakage as
they increment EAPI. I am confident
On 10/16/2011 12:00 AM, Paweł Hajdan, Jr. wrote:
On 10/15/11 2:42 AM, Dirkjan Ochtman wrote:
On Sat, Oct 15, 2011 at 03:54, Mike Gilbert flop...@gentoo.org wrote:
That would be an ok approach from my perspective: We could just change
line 14 of python.eclass and let package maintainers report
On Sat, Oct 1, 2011 at 3:16 PM, Paweł Hajdan, Jr.
phajdan...@gentoo.org wrote:
OK, so what are the _blocking_ reasons for no EAPI 4 support in
python.eclass yet?
I understand you have some complicated patches in flight etc etc, but
are they _required_ for the eclass not to break with EAPI 4?
On Fri, Oct 14, 2011 at 03:29:19PM -0400, Matt Turner wrote:
On Sat, Oct 1, 2011 at 3:16 PM, Pawe?? Hajdan, Jr.
phajdan...@gentoo.org wrote:
OK, so what are the _blocking_ reasons for no EAPI 4 support in
python.eclass yet?
I understand you have some complicated patches in flight etc
On 10/14/11 12:39 PM, Brian Harring wrote:
On Fri, Oct 14, 2011 at 03:29:19PM -0400, Matt Turner wrote:
On Sat, Oct 1, 2011 at 3:16 PM, Pawe?? Hajdan, Jr.
phajdan...@gentoo.org wrote:
OK, so what are the _blocking_ reasons for no EAPI 4 support in
python.eclass yet?
I understand you have
On Fri, Oct 14, 2011 at 4:20 PM, Paweł Hajdan, Jr.
phajdan...@gentoo.org wrote:
On 10/14/11 12:39 PM, Brian Harring wrote:
On Fri, Oct 14, 2011 at 03:29:19PM -0400, Matt Turner wrote:
On Sat, Oct 1, 2011 at 3:16 PM, Pawe?? Hajdan, Jr.
phajdan...@gentoo.org wrote:
OK, so what are the
On Fri, Oct 14, 2011 at 5:25 PM, Matthew Summers
quantumsumm...@gentoo.org wrote:
Its being worked on currently. There are many fairly difficult issues
to be worked through here.
That's kind of the question though. What's are the issues?
On 10/14/2011 5:28 PM, Matt Turner wrote:
On Fri, Oct 14, 2011 at 5:25 PM, Matthew Summers
quantumsumm...@gentoo.org wrote:
Its being worked on currently. There are many fairly difficult issues
to be worked through here.
That's kind of the question though. What's are the issues?
The only
Paweł Hajdan, Jr. schrieb:
On 10/14/11 12:39 PM, Brian Harring wrote:
On Fri, Oct 14, 2011 at 03:29:19PM -0400, Matt Turner wrote:
On Sat, Oct 1, 2011 at 3:16 PM, Pawe?? Hajdan, Jr.
phajdan...@gentoo.org wrote:
OK, so what are the _blocking_ reasons for no EAPI 4 support in
python.eclass
On 10/14/11 3:32 PM, Thomas Sachau wrote:
What do you expect the council to do?
Say it's OK to make python.eclass not die on EAPI-4. At least my use
case will not become broken by this.
Neither you nor the council can force anyone to do anything.
Not really. It should always be possible to
On Fri, Oct 14, 2011 at 05:52:59PM -0400, Mike Gilbert wrote:
It would be helpful if folks could brain storm a list of python related
packages to test under EAPI 4. I may have some time over the next few
weekends to work on this.
dev-vcs/git needs python eclasses to have EAPI4 so REQUIRED_USE
On Fri, 2011-10-14 at 22:53 +, Robin H. Johnson wrote:
dev-vcs/git needs python eclasses to have EAPI4 so REQUIRED_USE can be
used to solve bug #353657.
Similar problems in dev-vcs/subversion...
Regards,
Tony V.
signature.asc
Description: This is a digitally signed message part
On Fri, Oct 14, 2011 at 3:51 PM, Paweł Hajdan, Jr.
phajdan...@gentoo.org wrote:
On 10/14/11 3:32 PM, Thomas Sachau wrote:
What do you expect the council to do?
Say it's OK to make python.eclass not die on EAPI-4. At least my use
case will not become broken by this.
Neither you nor the
On 10/14/11 5:38 PM, Alec Warner wrote:
I believe op's point is that there is no one to escalate the problem
to; certainly the council members are not going to do the work
themselves and we already have our best people on it.
I'm aware of that. My point is that I think there are many scenarios
On 10/14/2011 09:11 PM, Paweł Hajdan, Jr. wrote:
On 10/14/11 5:38 PM, Alec Warner wrote:
I believe op's point is that there is no one to escalate the problem
to; certainly the council members are not going to do the work
themselves and we already have our best people on it.
I'm aware of
OK, so what are the _blocking_ reasons for no EAPI 4 support in
python.eclass yet?
I understand you have some complicated patches in flight etc etc, but
are they _required_ for the eclass not to break with EAPI 4?
My point is that I'd like to use pkg_pretend in packages that use
python.eclass
18 matches
Mail list logo
