> > What is the use-case for this level of control then, and why would it > be specific to RPM? >
Despite Alexander's words about this document, most of (I suppose, actually all) wide-used rpm-based distros use the same well-known rpm packages naming convention: red hat, opensuse, centos, oracle enterprise linux, fedora, ... There are a lot of useful tools in this huge world of enterprise-level distros, especially all those staff related to static security scans/audit and around SBOM collection and processing. Those tools rely on some basic rules of rpm naming for their analysis and do not handle architectures like "genericx86_64". I.e. this level of control opens for us a tremendous window of possibilities when our build pretends to be a mature distro. BR, Sergei
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#175836): https://lists.openembedded.org/g/openembedded-core/message/175836 Mute This Topic: https://lists.openembedded.org/mt/96233100/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
