On Fri, Nov 04, 2022 at 01:44:41PM +0100, Petr Menšík wrote: > If there are binaries with different build results, I think some > code should be refactored out of the binary itself. The common parts > can remain, but hardware specific parts should be moved to > dynamically loaded *.so files. The correct files should be loaded > depending on hardware found on the system. If auto-detection is > wrong, manual configuration via configuration file should be used > instead. I think this is right. In particular you cannot assume that "the hardware" is a thing which remains stable for the lifetime of a Fedora install. Sure, if you install Fedora on your laptop then the hardware is unlikely to change. But if you install Fedora on a VM then it can be moved and booted on a VM with different (virtual) hardware. And there's also the template case where someone prepares a disk image on one set of hardware (maybe virtual or physical) and then the disk image is used as a template to clone multiple systems from. Having autodetection at run time deals with this, having different hardware-specific RPMs installed does not. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW _______________________________________________ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
