The turn based strategy game wesnoth has moved development to a new new development tree - the 1.1.x line of wesnoth. Yesterday 1.1.1 was released and it is just great (TM). Could there be ebuilds for wesnoth-1.1.1 please (hard masked if you want)? It would be great if the 1.1.x line uses slot1 and the 1.0.x line uses slot0, but this is optional of cause. And please do not play wesnoth BEFORE you did the ebuild, cause it is too adicting ;-)
We generally don't do anything beta, pre-release, or development simply because then we'll have to support it. Yes, even if it is masked, we have to support it. You are more than welcome to attach an ebuild here for the development version and point people to this bug to get it, but we won't introduce a development branch into the tree. It's simply too much hassle to maintain and has caused too many problems for us in the past.
Created attachment 79445 [details] wesnoth-1.1.1.ebuild This is a modified 1.0.2 ebuild with a workaround for an upstream bug (https://gna.org/bugs/?func=detailitem&item_id=4999) added. This Wesnoth development release caused some severe memory problems when compilation came across multiplayer_connect.cpp: gcc wanted up to 1GB memory to get this done, I had to add additional swap space. (possible gcc 3.4.4 flaw/bug?) Upstream has been notified. (http://gna.org/bugs/?func=detailitem&item_id=5237)
(In reply to comment #2) > This Wesnoth development release caused some severe memory problems when > compilation came across multiplayer_connect.cpp: gcc wanted up to 1GB memory to > get this done, I had to add additional swap space. (possible gcc 3.4.4 > flaw/bug?) Same here when I tried to compile it - and I have gcc 3.4.4-r1 too.
Just in case anyone gets this problem, too: In my ~/.wesnoth/preferences file show_combat was set to "no" from some earlier Wesnoth installation; this is not configurable from the game itself, so make sure to set this to "yes" to see the new combat animations.
*** Bug 125013 has been marked as a duplicate of this bug. ***
*** Bug 125473 has been marked as a duplicate of this bug. ***
*** Bug 127646 has been marked as a duplicate of this bug. ***
*** Bug 128310 has been marked as a duplicate of this bug. ***
The development branch of wesnoth is more used than the stable branch, and the different versions are not compatible with each others so the 1.0.2 ebuild is a bit useless I understand why you don't want to include development versions, maybe the wesnoth team should change the names of the branches ... But, as it is done with enlightenment and others ebuilds, a wesnoth-9999.ebuild using the cvs could be included I can do the ebuild, but I'd like to know if it would end up as another duplicate of this bug or not
(In reply to comment #2) > Created an attachment (id=79445) [edit] > wesnoth-1.1.1.ebuild > ... A new release of wesnoth is available (wesnoth-1.1.4). You can find a gentoo ebuild on the wesnoth forum (made by Markus Schmeing): http://www.wesnoth.org/forum/viewtopic.php?t=11443 Everything works fine (no more memory problems with gcc-3.4.4)
*** Bug 140380 has been marked as a duplicate of this bug. ***
Version 1.1.8 is out and it is the first offical beta for the 1.2 release! The developers are asking people to help out and file any bugs they find. For more on how to file bugs for wesnoth there's an entry on their wiki: http://www.wesnoth.org/wiki/ReportingBugs You can just make a copy the old ebuild with the new name and it will work. # cp wesnoth-1.0.2.ebuild wesnoth-1.1.8.ebuild
*** Bug 143700 has been marked as a duplicate of this bug. ***
*** Bug 144178 has been marked as a duplicate of this bug. ***
