Once upon a time, R P Herrold <herrold@xxxxxxxxxxxx> said: > As an alternative, adding a 'virtual build requirement' such > as for: > BR: CCP-compiler > > and adding a manual: > Provides: CCP-compiler > > to: gcc-c++ > > and so forth, would make this a non-invasive change. Why ** > not ** choose such a route? There are a significant (but unknown number) of packages in Fedora that are probably only currently built and tested upstream with GCC compilers. Putting a virtual requires in the spec, before testing them with alternate compilers, is incorrect. Linux-developed software tends to have lots of hidden GCCisms, and I believe erring on the side of assuming that until tested and proven otherwise is the safe choice. Start by requiring the status quo; as packages are tested and proved to work with an alternate compiler, then the specs can be modified to allow alternate compilers. -- Chris Adams <linux@xxxxxxxxxxx> _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/FSOG74W7YNZUASAEUZK4VKR4WJCGMBJX/
