1 |
On Tue, 11 Oct 2011 19:41:21 -0600 |
2 |
Ryan Hill <dirtyepic@g.o> wrote: |
3 |
|
4 |
> > Isn't this the same situation with gcc stabilizations? Once the |
5 |
> > timeframe for fixing broken packages with e.g gcc-4.5 is passed, the |
6 |
> > remaining broken packages will be gone. |
7 |
> |
8 |
> Absolutely not. They aren't even masked. There are usually a few niche |
9 |
> packages that can't be fixed but are in use. People can switch to a previous |
10 |
> version if they ever have to rebuild them. |
11 |
|
12 |
To clarify: we keep old versions of gcc in the tree for a reason, and it's |
13 |
not because we're history buffs. "Doesn't build with GCC x.x" alone is never |
14 |
grounds for removal. "Is unmaintained and doesn't build with GCC x.x" is |
15 |
perfectly fine, however, and some people use the gcc trackers to identify such |
16 |
packages. Maybe that's the correlation you see. |
17 |
|
18 |
|
19 |
-- |
20 |
fonts, gcc-porting, it makes no sense how it makes no sense |
21 |
toolchain, wxwidgets but i'll take it free anytime |
22 |
@ gentoo.org EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 |