1 |
On Tue, 9 Apr 2013 22:24:16 +0200 |
2 |
Michał Górny <mgorny@g.o> wrote: |
3 |
|
4 |
> On Tue, 9 Apr 2013 15:24:10 -0400 |
5 |
> Mike Frysinger <vapier@g.o> wrote: |
6 |
> |
7 |
> > On Tuesday 09 April 2013 01:57:47 Michał Górny wrote: |
8 |
> > > On Mon, 8 Apr 2013 23:20:28 -0600 Ryan Hill wrote: |
9 |
> > > > If someone else wants to try and improve the situation, please feel |
10 |
> > > > free. |
11 |
> > > |
12 |
> > > Just to be sure -- would you be ok if we tried to inline some |
13 |
> > > of the eclass code into the ebuilds (future versions/revbumps)? |
14 |
> > |
15 |
> > not really. you can still build gcc-2.95 and newer with the current code, |
16 |
> > but the amount of "tc_version_is_at_least" is fairly low. from time to |
17 |
> > time, people also create their own gcc ebuild forks which use this eclass |
18 |
> > either because it's a completely different code base, orit has some serious |
19 |
> > patches that we aren't interested in carrying, or people want to |
20 |
> > experiment. current examples: kgcc64 msp430 gcc-apple. we've had other |
21 |
> > embedded works in the past, as well as hardened ones. |
22 |
> |
23 |
> Then please don't create a fake feeling like you're going to accept |
24 |
> help to improve the situation. |
25 |
|
26 |
These are things the eclass has to support and the restraints we have to work |
27 |
under. Don't throw a snit if you don't like the problem space. |
28 |
|
29 |
|
30 |
-- |
31 |
gcc-porting |
32 |
toolchain, wxwidgets by design, by neglect |
33 |
@ gentoo.org for a fact or just for effect |