GCC withdraw

[Daniel Kalchev]

On 23.08.13 14:16, Kurt Jaeger wrote:
> Hi!
>
>>> I have a patch that I intend to commit before the 10.0 code
>>> slush that removes GCC and libstdc++ from the default build on
>>> platforms where clang is the system compiler.  We definitely don't
>>> want to be supporting our 6-year-old versions of these for the
>>> lifetime of the 10.x branch.
>> Isn't it a POLA violation?
>>
>> As for me I expect something like this:
>> . 9.x gcc default and clang in base;
>> . 10.x clang default and gcc in base;
>> . 11.x gcc withdraw.
> If the 150 ports that only work with gcc, all work with a ports
> gcc and do not need the gcc from base, would the following be OK ?
>
> - 9.x gcc default and clang in base;
> - 10.x clang default and gcc in ports;
>

I believe this is the best idea so far. As long as these ports work with 
gcc in ports, that is.

For many of the "important" ports, they do get used together with other 
ports that already require newer gcc from ports anyway. So no additional 
pollution will be created.

Daniel