Removal of GCC from the buildroot
Removal GCC and friends from the buildroot
is different than
adding new conflicting BRs which impair Clang usability
On Mon, 9 Jul 2018,
Igor Gnatenko started:
> > I'm going to do this tomorrow.
> >
> > After which, I'm going to ask rel-eng to finally remove it from buildroot.
> >
> > This will happen before mass rebuild. Stay tuned.
Tomasz Kłoczko wrote:
> After adding explicite gcc/g++ in BuildRequires it will be
extreamly
> hard to switch use for example to use clang.
>
> Congratulation.
and this snipeing came in from: Przemek Klosowski:
Come on now...
You 'tutt tutt' this objection, but it seems that the
secondary effects of the change are not well thought through.
As an alternative, adding a 'virtual build requirement' such
as for:
BR: CCP-compiler
and adding a manual:
Provides: CCP-compiler
to: gcc-c++
and so forth, would make this a non-invasive change. Why **
not ** choose such a route?
Obviously, clang would also need a manual:
Provides: CCP-compiler
----------
What is the need to force breakage, rather than doing it in
'friendly' way?
-- Russ herrold