Hi, On 4/23/21 5:37 PM, Gary Buhrmaster wrote: > On Fri, Apr 23, 2021 at 3:19 PM Ben Cotton <bcotton@xxxxxxxxxx> wrote: >> >> https://fedoraproject.org/wiki/Changes/CompilerPolicy >> > > Ultimately, I think what the packaging guidelines should be if > the proposal is accepted are essentially: > > > > For C/C++ projects: > > If the upstream has no stated preference for the compiler, the > packager SHOULD use the system default compiler (i.e. GCC). > > If the upstream specifies a preference, in their documentation, > build, or support processes, the packager SHOULD follow > the direction of the upstream. > > The packager MAY, at their discretion, choose to use > an alternative compiler that is otherwise available in > Fedora. The reasons for those override choices > MUST be documented in the .spec file. +1 I think that this is a good way to formulate the guidelines around this. It also matches nicely with the firefox example from the changes page, I have heard others in this thread call the reasoning surrounding building firefox with llvm somewhat weak (I'm paraphrasing here), but firefox is a quite large project; and needlessly deviating from upstream really is not doing anyone any favors here IMHO. Regards, Hans _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
