* Luca Boccassi: >> * Zbigniew Jędrzejewski-Szmek: >> >> >> The general case of any statically linked code. It could be libgcc, >> startup files, the non-shared bits of glibc, static-only libraries, or >> header-only C++ libraries. > This would be indeed useful, but quite harder to do automagically I > think? It requires some level of toolchain support, in compilers and linkers. It's unlikely that this would use a JSON-based approach, though. I think what we want in the linker for this is that it de-duplicates and merges individual artifact identifiers, so that one ends up with a single string "glibc-2.34-7.fc35" instead of multiple copies of it. But I can't see us implementing JSON processing in the linker (all four of them). Thanks, Florian _______________________________________________ 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
