Remove gcc, gcc-c++ and make from minimal build root

[Miloslav Trmač]

> Dne 13.1.2015 v 08:12 Ralf Corsepius napsal(a):
> > On 01/13/2015 07:12 AM, Stanislav Ochotnicky wrote:
> >> On Tue 13 Jan 2015 01:35:26 AM CET Kevin Kofler wrote:
> >>> Vít Ondruch wrote:
> > I basically see several issues:
> >
> > 1. The sheer amount of packages being affect.
<snip data>
By all accounts we are talking an order of thousands of packages, i.e. thousands of hours spent on adjusting the BuildRequires.  Conservatively, that could have been hundreds of user-visible bugs fixed; why is the user-invisible, and often developer-invisible, build speedup worth these hundreds of bugs?


> > 3. There likely are many tiny problems under the hood (esp. in
> > packages primarily written in scripted languages), such as (yet
> > unknown and hidden) conditionally built
> > features/sub-components/sub-packages and conditional deps etc.
> 
> Definitely, something will bite us. Nobody claims the opposite. Nobody
> says its piece of cake, lets do it for F22.

Looking at this in reverse, if we had the option to save thousands of hours and avoid unknown regressions by spending 20 seconds extra per build, why yes, we would very likely take it.  So shouldn’t we, consistently, not spend those thousands of hours and a risk of “definitely something will bite us” to save 20 seconds per build?

Don’t get me wrong, speeding up builds is good in principle; but we have to consider the opportunity cost.  Couldn’t we find a way to completely automate away this decision so that the builds are fast and the packagers don’t have to care?
     Mirek