This has come up in #438
For now there is no way to use the dependency system to configure the system
depending on hardware or other properties. There is something like this in
libzypp (used by openSUSE) which injects system Provides into the transaction.
Quoting from #438:
Main use of such a mechanism will installing packages for hardware support
based on the presence of said hardware. This will in most cases require pattern
matching as addressing each hardware variant is not practical. IIRC libzypp
does have some special idiom for this that uses patterns.
The next thing is that most package installations happen on an empty system. So
any mechanism that relies too heavily on scripts/programs on the system is
doomed to fail. Especially as the dependency resolution is done before anything
gets installed.
One possible implementation could be a "exists(FNMATCH)" special name. That
would look into the actual file system and not rely on the rpm database. But
someone still needs to evaluate if this is feasible and actually solving the
real world use cases - especially during first installation.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/446
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
