Description of problem: Apologies in advance if this is not the place to file this, I've googled and found only a handful of other posts in various places with the same issue and suggestions in these places to file a bug: the Fedora page for filing bugs did not suggest going anywhere else also. If there's somewhere else I should stick this please tell me. The only version of this package available is the development version, which is an issue both because it is inherently unstable and because it lacks online players and add-ons both of which overwhelmingly stick to the stable version only. Indeed the Wesnoth site itself has 1.16.6 as the version at time of writing this package is at 1.17.7. From what I can gather usually even numbers are stable and odd are development. Version-Release number of selected component (if applicable): 1.17.7 How reproducible: n/a Steps to Reproduce: n/a Actual results: Addons and other players not available, game is not guaranteed to be stable/finished. For example compare the size of the addons for stable https://www.wesnoth.org/addons/1.16/ vs the development branch https://www.wesnoth.org/addons/1.17/ Both of these elements are somewhat essential parts of the experience. Expected results: Ideally installing only wesnoth should give the stable package and something like wesnoth-development for the dev version. If only one then the stable one only. Additional info: n/a
Some links for reference: https://wiki.wesnoth.org/Download - download page showing stable/development split https://wiki.wesnoth.org/WesnothBinariesLinux - most other distros provide either both or stable only
Hi! The rationale for shipping the development version is the relationship between the Fedora release cycle and the wesnoth development cycle. There have been several instances where the stable version uses something deprecated in Fedora, or would no longer build on the newest gcc, necessitating un update to the development version. I've considered shipping two editions in the past, but in many cases the stable version would be unbuildable for at least two releases.
Understood, that does indeed sound like a tricky problem and perhaps something that is more on the upstream devs to try and keep a little more up to date.
It's just one of the realities of the intersection of a fast-moving OS distribution and a large and complex project. For example, moving Wesnoth totally off of Python 2 was non-trivial. :)
*** Bug 2203604 has been marked as a duplicate of this bug. ***
wesnoth developer have solve this bug. details: https://bugzilla.redhat.com/show_bug.cgi?id=2203604