1 |
Alec Warner posted on Tue, 10 Oct 2017 15:28:41 -0400 as excerpted: |
2 |
|
3 |
>> Please consider switching from your current 13.0 profile to the |
4 |
>> corresponding 17.0 profile soon after GCC 6.4.0 has been stabilized on |
5 |
>> your architecture. The 13.0 profiles will be deprecated and removed in |
6 |
>> the near future. |
7 |
>> |
8 |
>> |
9 |
> Can you commit to a deadline on this? |
10 |
> |
11 |
> Its OK to be wrong (e.g. say 1 month but remove in 3); but "near future" |
12 |
> is not actionable by readers. |
13 |
|
14 |
Will the 13.0 profiles be removed all together, or per-arch? |
15 |
|
16 |
If they're removed all at the same time, then the time-limiting factor |
17 |
will certainly be how long it takes the last arch to stabilize gcc-6.4+, |
18 |
something that's likely not entirely predictable but that might take some |
19 |
time, given gentoo's known issues with straggling archs. |
20 |
|
21 |
If the existing profiles will be deprecated and removed per-arch, with |
22 |
some fixed time after gcc-6.4+ stabilizes on that arch as a goal, then |
23 |
the time for most popular and best maintained archs may be predicted now, |
24 |
but the time will differ for each one, so the best that could be done |
25 |
would be either a time range or a list of the known ones, with presently |
26 |
unknowns being added to the list in further revisions of the news item. |
27 |
|
28 |
The other alternative might be to word it something like (1 year can be 6 |
29 |
months or whatever instead, if that works better): |
30 |
|
31 |
"13.0 profiles are set to be removed one year after the last arch |
32 |
stabilizes gcc-6.4+, with the goal for the gcc stabilization being the |
33 |
end of 2017, meaning 13.0 profile removal is planned for the end of 2018 |
34 |
if all archs meet their gcc-6.4+ stabilization goal." |
35 |
|
36 |
-- |
37 |
Duncan - List replies preferred. No HTML msgs. |
38 |
"Every nonfree program has a lord, a master -- |
39 |
and if you use the program, he is your master." Richard Stallman |