See summary. They were kind enough to give it the same name, so if you previously emerged 0.2.2b you'll have digest problems.
Created attachment 20090 [details, diff] Patch from 0.2.2b.ebuild to 0.3.0b.ebuild
I've been speaking with some of the developers, I'll get them to change the tarball to reflect version as soon as I can.
For your convenience: http://hosted.tribalwar.com/legends/bugtracker/bug_view_page.php?bug_id=0000267
Created attachment 20402 [details] legends-0.3.0b.ebuild This is my version of the ebuild (not a patch). Removal of some useless chmods, and actually makes USE of `dedicated`. I also changed the license. The TGE license doesn't really apply, it was more of a placeholder until they actually decided on something. This release, they included a copyright statement and disclaimer in the documentation. See Bug 32975. And Donnie, please do see if you can get them to add version numbers to their package names.
Created attachment 20406 [details] legends-0.3.0b.ebuild mr. bones has schooled^H^H^H^H^H^H^H^H informed me that an "as-is" license exists. This ebuild is now using that.
Created attachment 20497 [details, diff] Patch from 0.2.2b.ebuild to 0.3.0.ebuild It makes things easier to name it 0.3.0.ebuild instead of 0.3.0b, and since the b actually signifies beta and not an actual release "b," this makes sense. This patch incorporates all above changes, and they fixed the versioning upstream.
Created attachment 20498 [details, diff] Oops, attached the wrong patch last time.
Why a patch? Just attach the whole ebuild with the CVS header information removed. You are much more likely to get it committed like that. Once yours is up, I'll obsolete mine. Thank you for talking them into getting the versioning fixed.
Because it's a lot more work for the committer to see what changed if you keep posting a full ebuild (this gets exponentially more difficult as the ebuild size increases). Presumably said committer is not going to blindly commit changes. If you post a patch, he simply clicks the link. If you post a full ebuild, he has click the link, save it to his machine, and diff it against the current ebuild to get the same result. Perhaps for some people you are right, but I personally prefer to receive patches instead of full ebuilds on my bugs.
Comment on attachment 20406 [details] legends-0.3.0b.ebuild Removing my obsolete ebuild.
Added to CVS. Thanks for the bug report and ebuild. For future reference, in the games we prefer whole ebuilds since it's easier to download and try out quickly. Different strokes, etc. ;-)
Keith, you win. =P
