The make package use 539k of space. And for gcc + C++ it's more than 30 Mo.
Does it really worth the effort on changing all the dependent packages ?

----- Mail original -----
De: "Zbigniew Jędrzejewski-Szmek" <zbys...@in.waw.pl>
À: "Development discussions related to Fedora" <devel@lists.fedoraproject.org>
Envoyé: Jeudi 5 Novembre 2020 14:42:08
Objet: Re: Fedora 34 Change proposal: Remove make from BuildRoot (System-Wide 
Change)

On Thu, Nov 05, 2020 at 01:13:47PM +0100, Fabio Valentini wrote:
> On Wed, Nov 4, 2020 at 9:46 PM Neal Gompa <ngomp...@gmail.com> wrote:
> 
> (snip)
> 
> >
> > Koji/Brew disables weak dependencies. The weak dependency would be for
> > developer convenience.
> >
> > > If the change was automated and you did not have to do anything would
> > > you still be opposed to having your spec files updated with
> > > BuildRequires: make
> > >
> >
> > You still need BR: make.
> 
> Couldn't we add something like this to the cmake package?
> 
> Requires: (make or ninja)
> Suggests: make
> 
> Which would make sure at least *one* of the available backends is
> installed, and would make it prefer make if ninja is not specified
> explicitly.

It that works, it'd be great.

Zbyszek
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Reply via email to