On Fri, 31 Jul 2009, Miroslav Lichvar wrote:
That might be a nice createrepo feature to add such conflicts.
That would only help you if you only have a single repository - which we NEVER do b/c of fedora + updates + updates-testing.
Yes, but that's not what I'm talking about. I mean the explicit conflicts between current versions of packages. I.e. the thing that makes the complexity exponential. For example: package A: depends on X package B: conflicts with D package C: provides X package D: provides X yum install A B fails here as it tries to install A B D. The solution is to install A B C.
And you've tested that yum doesn't work in this case? Putting together a unittest for it should be pretty straightforward.
-sv -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
