* Neal Gompa: > This is probably a bad idea, since that deliberately breaks things for > things that expect it to be there. If we *really* want to get rid of > this (and I'm not entirely convinced we should), why not just make an > alternative build subpackage and make the two conflict? One with Guile > support and one without? Then if something needs Guile integration for > Make, for example, they can install "make-guile" instead of "make".
With those explicit dependencies on “make”, installing “make-guile” wouldn't allow you to build much else anymore. “make-guile” could perhaps provide “make”, but I'm a bit wary of such ambiguous dependencies among core packages. In my opinion, the presence of Guile support in make is a disservice to our users because other distributions (including downstreams) do not have it, so it creates non-portable programs if it is ever used. > Also "shrink the buildroot" for Make isn't a good enough reason to do > this, since we don't even include Make in the buildroot by default > anymore[1]. > > [1]: https://fedoraproject.org/wiki/Changes/Remove_make_from_BuildRoot It still has to be downloaded and installed for most C/C++ builds. Thanks, Florian -- Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill _______________________________________________ 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
