Gentoo Archives: gentoo-dev

From: Richard Fish <bigfish@××××××××××.org>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: Portage: missing pieces
Date: Sun, 09 Jul 2006 20:45:51
Message-Id: 7573e9640607091342g594be217n4874028a6074948c@mail.gmail.com
In Reply to: [gentoo-dev] Re: Portage: missing pieces by Molle Bestefich
1 On 7/9/06, Molle Bestefich <molle.bestefich@×××××.com> wrote:
2 >
3 > Try reading the bug - users are basically being shoved off with an
4 > arrogant silence and a stamp on their forehead saying INVALID.
5
6 *Sigh*. You really should post to -user first.
7
8 The expectation here is that when a new version of gcc is stabilized,
9 that users will upgrade to that in a reasonable amount of time, and
10 use that (by selecting it with gcc-config) for compiling all new
11 updates. FYI, gcc-3.4.4-r1 was stabilized on 2-Dec-2005, and the
12 current stable is 3.4.6-r1 since May 29th.
13
14 The devs can *not* be expected to verify that all software in portage
15 builds with all versions of gcc in portage. For example, there is
16 still an ebuild for gcc-2.95.3! But that is _not_ to be used for
17 compiling new updates.
18
19 The alternative here is that old versions of gcc disappear from
20 portage, but that causes a problem for those who need those versions
21 for some reason, such as compiling non-gentoo software.
22
23 > Nothing personal against Jakub Moc who probably has a lot to do, but
24 > the handling of relevant issues raised in the bugzilla is just
25 > unacceptable.
26
27 What, exactly, do you find unacceptable in "Your gcc version is
28 outdated and unsupported"?
29
30 I suppose portage could be enhanced to have a
31 is_gcc_version_supported() check, but I'm not sure how useful that
32 would be.
33
34 > What's the state of Portage and Gentoo in general? Is there not
35 > enough hands to do a proper job? Or is it just that none of the devs
36 > see what's wrong because bugs are wrongly being closed marked
37 > "INVALID" such as the above when they're in fact not?
38
39 If you want to test compiling every version of every package in
40 portage with all 21 versions (16 if you assume all -rX versions are
41 compatible, or /only 9/ if you only consider stable x86 versions) of
42 gcc that are currently in portage, and submit patches when things
43 fail, go ahead. BTW, your patches cannot remove the ability to use
44 improvements that are only available in newer stable versions of gcc,
45 such as -fvisibility=hidden.
46
47 -Richard
48 --
49 gentoo-dev@g.o mailing list