Gentoo Archives: gentoo-dev

From: "Harald van Dijk" <truedfx@g.o>
To: gentoo-dev@l.g.o
Subject: Re: Gentoo vs GNU toolchain (was Re: [gentoo-dev] Replacing cpu-feature USE flags)
Date: Fri, 07 Jul 2006 23:10:43
Message-Id: 20060707230445.GA3800@gentoo.org
In Reply to: Re: Gentoo vs GNU toolchain (was Re: [gentoo-dev] Replacing cpu-feature USE flags) by Mike Frysinger
1 On Fri, Jul 07, 2006 at 06:13:27PM -0400, Mike Frysinger wrote:
2 > ignored *what* then ? you requested USE=vanilla control ssp, i said no and
3 > i'll add support for USE=nossp ... you requested USE/stub control, i said no,
4 > go delete the stubs
5
6 USE=nossp existed before USE=vanilla did. To be sure I'm remembering
7 right, I checked `cvs log toolchain.eclass`. In order, probably skipping
8 a few steps:
9
10 1- No SSP
11 2- Choice between SSP [USE=-nossp] and stub patches [USE=nossp].
12 USE=vanilla didn't exist.
13 3- Choice between SSP [USE="-nossp -vanilla"], stub patches
14 [USE="nossp -vanilla"], and nothing [USE="vanilla"]
15 4- Choice between SSP [USE=-nossp] and stub patches [USE=nossp]
16 USE=vanilla exists but has no effect on SSP.
17
18 It was during 2 that I asked for a way to disable stub patches for
19 myself (and not as part of the official ebuild), and you said to delete
20 them. That was good enough for me during 2. We are now in 4.
21
22 > i dont see what else you're referring to ... be specific, vague claims only
23 > lead to wasting of both our times
24
25 I hope this is specific enough: toolchain.eclass revision 1.234
26 (separating ssp/... from vanilla) log message:
27 "ssp/pie/htb have their own USE flags sep from vanilla, so people can
28 utilize those"
29 when in fact the old USE=vanilla behaviour is unavailable now. You have
30 never (as far as I know) answered whether it was intended to keep the
31 old behaviour as an option, and if it wasn't, why the log message is
32 what it is.
33
34 > all bets are off now then ... with Halcy0n leaving us, that leaves me as the
35 > only person maintaining the toolchain (there are few devs who contribute
36 > fixes for their ports and it helps out a ton, but that doesnt really count as
37 > being fully responsible for the toolchain packages).
38
39 I'll keep that in mind, I wasn't aware that the other toolchain guys
40 handle specific parts of the toolchain packages only. Even if I disagree
41 with some specific decisions, nice job overall, then.
42 --
43 gentoo-dev@g.o mailing list

Replies