1 |
On 05/10/2017 03:29 PM, Andreas K. Huettel wrote: |
2 |
> Am Mittwoch, 10. Mai 2017, 13:58:56 CEST schrieb Dirkjan Ochtman: |
3 |
>> On Wed, May 10, 2017 at 11:19 AM, Kristian Fiskerstrand <k_f@g.o> |
4 |
> wrote: |
5 |
>>> Sounds like a reasonable action plan. The consequences of such a change |
6 |
>>> definitely seems to be sufficiently high to merit a proper migration |
7 |
>>> plan which doesn't seem to have been established at this point. Whether |
8 |
>>> that can be added to a later point with gcc6 (e.g by adding a new |
9 |
>>> profile, or a later point release) I don't have strong opinions on, but |
10 |
>>> there should be a plan and proper overview of the consequences. |
11 |
>> |
12 |
>> Yeah, I think I agree. From the discussions so far, I think that we |
13 |
>> should definitely aim for making pie the default for everyone (on |
14 |
>> arches where it makes sense), but doing it in the gcc-6 now which has |
15 |
>> seen only a short period of testing so far seems a bit hasty based on |
16 |
>> data from the messages that I've seen in these threads so far. |
17 |
> |
18 |
> Actually the idea I like best so far is Jason's profile suggestion. |
19 |
> |
20 |
> * package.use.mask gcc[pie] in the 13.0 profiles |
21 |
> |
22 |
> * generate a new set of profiles 17.0 where it's package.use.forced |
23 |
> * tell people they may have to rebuild world when they switch |
24 |
> |
25 |
> -> This would also give us some time to discuss what other changes we might |
26 |
> make with the transition to the new profiles. |
27 |
> |
28 |
> -> Also, this means the transition is independent of gcc release timing. |
29 |
> |
30 |
> (We just need to be careful since hardened also inherits 13.0, so the setting |
31 |
> must be overridden there. As far as I can see that's already done there |
32 |
> though.) |
33 |
> |
34 |
|
35 |
+1 |
36 |
|
37 |
-- |
38 |
Kristian Fiskerstrand |
39 |
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net |
40 |
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 |