On Mon, Mar 09, 2020 at 12:11:42PM -0500, Bruno Wolff III wrote: > On Mon, Mar 09, 2020 at 18:11:32 +0100, > Fabio Valentini <decathorpe@xxxxxxxxx> wrote: > >On Mon, Mar 9, 2020 at 5:57 PM Bruno Wolff III <bruno@xxxxxxxx> wrote: > > > >I'm also not sure how you would detect that from the package metadata > >... query all packages for their file contents, and then show > >conflicts when two packages own the same file, but do not explicitly > >Conflict? I think that's probably too simplistic ... > > I don't think that practice is banned currently, It is, see https://docs.fedoraproject.org/en-US/packaging-guidelines/Conflicts/. Files should be renamed to remove the conflict, and if not possible, explicit Conflicts must be added. > but it would probably cut down on mistakes if it were. Having two > sources of truth that are supposed to be identical, makes it easy > for people to make a mistake. Yes, it is super annoying to users, because the error is not reported in the initial stage, but only after all packages have been downloaded. Zbyszek _______________________________________________ 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
