| |
@@ -3,3 +3,17 @@
|
| |
|
| |
[[sect-c]]
|
| |
= C
|
| |
+
|
| |
+ == GCC removed from the default buildroot in Koji
|
| |
+
|
| |
+ Since the first release of Fedora, `gcc` and `gcc-{cpp}` were installed by default in every buildroot.
|
| |
+ At that time this was useful for most packages as they were typically written in C or {cpp}.
|
| |
+ However, many packages today are written in other languages and they do not need a C/{cpp} compiler, and at the same time, installing `gcc` and `gcc-{cpp}` takes time which is wasted if they are not required.
|
| |
+
|
| |
+ Starting with this release, `gcc` and `gcc-{cpp}` are no longer installed by default in every buildroot, which results in quicker builds for packages which do not require them, better package compliance with the link:++https://fedoraproject.org/wiki/Packaging:Guidelines++[Packaging Guidelines], and a cleaner buildroot environment.
|
| |
+
|
| |
+ You can test that your Fedora package still builds after the change by running `mock` or `fedpkg mockbuild` with a modified configuration file that excludes `gcc` and `gcc-{cpp}` from the buildroot.
|
| |
+ Detailed instructions have been provided on the link:++https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/4GUVCYWZ2BS3YHIS7ZFHJO5MHIIUQY3S/++[devel mailing list].
|
| |
+
|
| |
+ If your package does require `gcc` or `gcc-{cpp}` and fails to build with them removed from the default buildroot, add the appropriate `BuildRequires`.
|
| |
+ See link:++https://fedoraproject.org/wiki/Packaging:C_and_C%2B%2B#BuildRequires_and_Requires++[Packaging:C and {cpp}] and link:++https://fedoraproject.org/wiki/Packaging:Guidelines#Build-Time_Dependencies_.28BuildRequires.29++[Fedora Packaging Guidelines] for details about `BuildRequires`.
|
| |
Fixes #123.