Description of problem: gnome-games conflicts with gnuchess, similar to bug #214589 Version-Release number of selected component (if applicable): gnome-games-2.17.2-2.fc7 How reproducible: Steps to Reproduce: 1. install gnuchess-5.07-10.fc6 2. Try to install gnome-games-2.17.2-2.fc7 3. Actual results: Expected results: Additional info: Probably needs a Obsoletes/Provides pair similar to the fix for #214589
I've added a Provides/Obsoletes in 2.17.2-3.fc7
I'd be happier with a Conflicts instead of Obsoletes, so people who prefer (non-gnome users ;-) could still install gnuchess
And wouldn't it have made more sense to actually have gnome-games depend on the existing gnuchess rather than just sucking it into gnome-games? Otherwise, anything that wants to use the gnuchess engine now has to depend on gnome-games which seems kind of wrong.
Fair enough. We can revisit that once the core/extras wall is falling. I don't think I can add a requires against an extras package right now. And moving things from extras to core would be silly at this point, since everything is bound to move the other direction soon.
Changed to Conflicts: for now.
Hi! I'd be very interested in suggestions for good ways to solve this. Currently there is the --disable-gnuchess parameter which you can pass to configure if you don't want to compile gnuchess as part of gnome-games.
Hi, I guess we can just drop gnuchess from gnome-games and direct people to pull it from extras.
This isn't conflicting now that I can see, correct?
Looks like it. gnuchess has /usr/bin/gnuchess gnome-games has /usr/bin/glchess and /usr/bin/gnome-gnuchess So I guess the conflict got removed by prefixing gnome-. Still, it would be much better to simply require gnuchess, now that we can, instead of shipping the same program under 2 different names
[hans@shalem devel]$ rpm -q gnome-games gnuchess gnome-games-2.18.1.1-1.fc7.x86_64 gnuchess-5.07-10.fc6.x86_64 And I didn't use --force or anything, closing.
Hmm, maybe that was to quick, re-opening and changing summary to match what this bug is now about, sorry.
Should be easy, add --disable-gnuchess to %configure and a "Requires: gnuchess"
The next rawhide push will include gnome-games-2.19.4-3.fc8, which fixes this.