#9503 Verify CompilerPolicy system wide change proposal does not impact release engineering
Closed: Fixed 10 months ago by mohanboddu. Opened 10 months ago by law.

  • Describe the issue
    Evaluation of Fedora 33 change proposal "CompilerPolicy" to ensure it does not require releng coordination to implement/deploy.

https://fedoraproject.org/wiki/Changes/CompilerPolicy

In simplest terms, Fedora has historically required packages to build with GCC unless the upstream project only supports building with Clang/LLVM. I'm recommending that policy be changed, allowing Fedora packages to use the same compilers as the upstream project recommends.

No mass rebuilding is necessary, and there is no specific timeline by which packages need to change. This is strictly to get the policy changed to reduce friction for Fedora developers/packagers.

  • When do you need this? 2020/06/17

  • When is this no longer needed or useful? N/A

  • If we cannot complete your request, what is the impact?
    We'd be unable to loosen policies WRT compiler usage for package builds which in turn forces Fedora developers to continue to waste time fixing packages such as Firefox or Chromium to work with GCC when they could just compile with LLVM per the upstream project's preferences.


@law No releng work is needed since its just a policy change.

Thanks for checking though.

Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
- Issue tagged with: change-noreleng, changes, f33

10 months ago

Login to comment on this ticket.

Metadata