| 1 |
Dnia 2013-09-03, o godz. 11:53:22 |
| 2 |
Markos Chandras <hwoarang@g.o> napisał(a): |
| 3 |
|
| 4 |
> On 3 September 2013 11:45, Michał Górny <mgorny@g.o> wrote: |
| 5 |
> > Hello, all. |
| 6 |
> > |
| 7 |
> > |
| 8 |
> > I'm attaching git-r3.eclass and a patch to git-2.eclass that adds |
| 9 |
> > ability to use git-r3 internally via make.conf switch. |
| 10 |
> |
| 11 |
> I am a bit skeptical about this. Why would someone want to do this |
| 12 |
> apart from testing the git-r3 eclass without touching |
| 13 |
> the existing git-r2 compatible ebuilds? And why do you want to do that in |
| 14 |
> the first place? If the maintainer is happy with how git-r2 works with |
| 15 |
> his ebuilds |
| 16 |
> I see no reason to allow users to silently override that eclass. |
| 17 |
|
| 18 |
The goal is to give git-r3 most testing it could get before it gets |
| 19 |
widely used. I'd prefer catching corner cases sooner than later. |
| 20 |
|
| 21 |
-- |
| 22 |
Best regards, |
| 23 |
Michał Górny |
Archives