Installing multiple packages risks conflict even before programs run, apparently due to dependencies. For that reason, Red Hat no longer supports an Everything installation. (See <https://bugzilla.redhat.com/show_bug.cgi?id=503880>.) That principle suggests, however, that any two or more pkgs. could conflict, and there are hundreds available just on a DVD, even before counting remote repositories. It could even occur with one package if it has a conflict with the kernel that hasn't been discovered.
Possible problems are dependencies for the same file in the same path but for diifferent versions of the file and mandatory absence of a dependency when another program requires presence.
That leaves a problem when installing. What packages can we install without conflicts? Or how can we fix the conflicts?
As an alternative, I think a public list of dependencies, including mandatory absences of dependencies, would help. The list should start with dep specifications, but if a clash suggests an error in programming, we should allow for error in a dep spec by allowing other people to add corrective observations. Even rare conflicts need to be known.
Is there such a list or is it an inadequate solution or is it bad idea or should it be created?
If it's a good idea, is setting up the list only feasible for distribution engineers or can anyone just start a list? The problem, I assume, is in collecting all the specs that apply to any single spin or more, and I doubt that posting a general message asking .all programmers whose products might be in a spin or a repo will get much response. Is there a better way?