FS#67143 - [range-v3] installed file /usr/include/module.modulemap will conflict with other packages

Attached to Project: Community Packages
Opened by Abdó Roig-Maranges (abdo) - Sunday, 28 June 2020, 22:38 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Monday, 27 July 2020, 08:13 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

range-v3 package installs a C++20 module map at /usr/include/module.modulemap, which will conflict with other packages that start doing the same. I noticed this because of a conflict with root-cuda.

Additional info:
* package version(s) 0.10.0-1

I am not certain of what would be the correct route here. The only other modulemap I have on my system is from libc++ at /usr/include/c++/v1/module.modulemap. So probably we should install it on /usr/include/range/v3/module.modulemap. This implies changing the header paths inside the modulemap, as they currently appear to be relative from /usr/include
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Monday, 27 July 2020, 08:13 GMT
Reason for closing:  Fixed
Comment by Sven-Hendrik Haase (Svenstaro) - Monday, 29 June 2020, 01:41 GMT
We could patch this downstream but I get the feeling that this is something that upstream should know about and fix on their end. Could you report this and link the issue here? They appear to be pretty responsive.
Comment by Abdó Roig-Maranges (abdo) - Monday, 29 June 2020, 21:52 GMT
Upstream issue: https://github.com/ericniebler/range-v3/issues/1522

Loading...