[Fedora-packaging] Conflicts

Michael Schwendt bugs.michael at gmx.net
Fri Mar 4 16:12:19 UTC 2005

What is the official policy about packages in Fedora Extras which
marked as conflicting with eachother?

E.g. Sylpheed (dropped from Rawhide) and Sylpheed-claws share file names
for main binary, manual page, pixmap file, desktop file. And since
Sylpheed-claws is the feature-enhanced bleeding edge development fork of
Sylpheed, there may be other conflicts. While this particular conflict
could be resolved by renaming the files, this would be contrary to what
upstream does.

As another example, gpgme03-devel and gpgme-devel. Used to building
in clean build environments where only the needed build requirements
are pulled in, there was no need to relocate either package and make
it possible to install both at once.

I think there are other extras which conflict because they provide same
or similar functionality, not limited to "leafnode" and "suck",
"oidentd" and "pidentd" (core), "proftd" and "vsftpd anonftp" (core).

Where do we go from here?

More information about the Fedora-packaging mailing list