On Fri, Dec 14, 2018 at 3:09 PM Igor Gnatenko <ignatenkobrain@xxxxxxxxxxxxxxxxx> wrote: > > That makes sense that we can do something like this from DNF code.. > However, it would be kinda hard to do any dependency resolution > checks.. > > Although we already have one which is module(platform:$PLATFORM_ID) > which is automatically populated from os-release by libdnf. Which is > actually causing problems during upgrade. > > I like both approaches. > Is there a reason stuff like this isn't available from RPM itself somehow? It seems like it'd make sense to just make this available as some kind of special Provides property, since RPM knows about it and would allow for dependency resolution to not be dependent on DNF... Failing that, since we apparently have this already for module() Provides, could we do this for system-architecture() too? I'd rather not mess with fedora-release for this... -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
