1 |
On Wed, 10 Apr 2013 16:22:29 -0400 |
2 |
Rich Freeman <rich0@g.o> wrote: |
3 |
|
4 |
> On Wed, Apr 10, 2013 at 3:30 PM, Mike Frysinger <vapier@g.o> wrote: |
5 |
> > we can could create a "toolchain-stable.eclass". whenever we stabilize a |
6 |
> > new version, we copy the current toolchain.eclass to |
7 |
> > toolchain-stable.eclass and change the newly stabilized ebuild to inherit |
8 |
> > that instead. |
9 |
|
10 |
That might worth a shot. |
11 |
|
12 |
> toolchain.eclass is only used by gcc, kgcc64, and gcc-apple. Would it |
13 |
> just make more sense to inline it? That makes all these issues go |
14 |
> away - each version has its own independent quality process and there |
15 |
> is no risk of changes breaking things across versions. |
16 |
|
17 |
While that's true, we often do make changes that need to be applied to all |
18 |
versions. The more each ebuild diverges from each other, the greater the |
19 |
likelihood of conflicts that will have to be individually inspected. |
20 |
|
21 |
I used to inline parts of toolchain_src_unpack in the live vcs ebuilds and |
22 |
I constantly had to sync them to the eclass by hand. And that's just 3 |
23 |
ebuilds. There are over 200 of them in the toolchain overlay. |
24 |
|
25 |
|
26 |
-- |
27 |
gcc-porting |
28 |
toolchain, wxwidgets by design, by neglect |
29 |
@ gentoo.org for a fact or just for effect |