1 |
All, |
2 |
|
3 |
the following is a comment Mike made about the status of glibc in an |
4 |
earlier thread on this list: |
5 |
|
6 |
On Sun, Aug 03, 2014 at 09:16:52AM -0400, Mike Frysinger wrote: |
7 |
> upstream glibc has dropped support for older Linux kernels. your choices: |
8 |
> - upgrade your kernel |
9 |
> - switch to a different C library |
10 |
> - stick with glibc-2.19 for a while |
11 |
> |
12 |
> be warned though there are no plans atm to backport things to glibc-2.19. |
13 |
> this includes security fixes, but more importantly as time moves on, making |
14 |
> newer gcc versions sanely compile glibc. we've kept older glibc versions |
15 |
> around to be nice, and on a part time basis for cross-compiling, but none of |
16 |
> those are given priority. i.e. fixes come as people feel like doing them. |
17 |
> |
18 |
> certainly once glibc-2.20+ goes stable, there is no expectation let alone |
19 |
> requirement that packages in the tree be kept working with older glibc |
20 |
> versions. the maintenance cost there is unreasonable. |
21 |
> |
22 |
> i guess if you're stuck on old crap, now would be a good time to start |
23 |
> preparing to unstick your crap. glibc-2.20 will most likely be in ~arch in |
24 |
> the next 6 months. |
25 |
> -mike |
26 |
|
27 |
Since glibc-2.19-r1 is stable everywhere, what I want to know is whether |
28 |
we can remove versions *prior* to 2.19-r1 at this point. |
29 |
|
30 |
If we do, that makes it easy to fix bug 478764 [1], because there would |
31 |
only be three versions of glibc we have to worry about. |
32 |
|
33 |
thoughts? |
34 |
|
35 |
William |
36 |
|
37 |
[1] https://bugs.gentoo.org/show_bug.cgi?id=478764 |