Here is my UFO2000 live SVN ebuild based on ufo2000-0.4.0.353.ebuild from the portage tree. Reasons to have live SVN ebuild are the following: currently the latest unstable versions of UFO2000 contain so many improvements and new features that almost nobody is using the stable version for network games now. In addition, server that is used for stable versions of the game at lxnt.info:2000 is currently down. So the only opportunity to play network games for the players is to use the latest unstable versions of the game and the server at lxnt.info:2001 (that is used for testing unstable versions). There is one problem though, unstable versions of UFO2000 get released too often and introduce incompatibilities sometimes that require users to upgrade. Submitting ebuilds for every development version would put too much work on gentoo portage tree maintainers and in addition there will be no guarantee that these ebuilds can be accepted in time (before they get outdated by the next unstable version of UFO2000). We have plans of releasing the next stable version in the near future. But we would like gentoo users to test the game before it gets promoted to stable status in order to avoid any unexpected bugs. In addition, the development process most likely will remain the same - frequent unstable releases for the users to test all the new features and report bugs earlier. So this live SVN ebuild will be useful even after this next stable version gets released. UFO2000 home page: http://ufo2000.sourceforge.net/ Wiki page with the links to the latest unstable versions of the game: http://ufo2000.lxnt.info/pmwiki/index.php/Main/DevelopmentVersion UFO2000 server statistics page (for unstable versions): http://ufo2000.lxnt.info/results.php Some more comments: ~ppc removed as we have information that UFO2000 does not work on big endian machines yet. -- Best regards, Serge Semashko (one of the UFO2000 developers)
Created attachment 44873 [details] ufo2000-svn-0.4.1.ebuild
We won't add a "live" cvs/svn ebuild. Now, if it were a snapshot, we wouldn't have a problem with that. The reason is that we are going to be the ones to get bugs for anything in our tree. If it is a "live" ebuild, then we have no way of guaranteeing that what is in your repository compiles. It is simply a matter of not wanting to put something in the tree that could potentially be broken. You could REOPEN this with a snapshot, and we would add that to the tree, since it would be static and unchanging, and therefore possible to do QA and bug fixes against.
Created attachment 45467 [details] ufo2000-0.4.1.622.ebuild Here is a ebuild for the latest ufo2000 svn snapshot at this moment (revision 606).
Reopening this bugreport with a snapshot as you have suggested.
Version bump (only name change "ufo2000-0.4.1.606.ebuild" -> "ufo2000-0.4.1.611.ebuild")
Version bump (only name change "ufo2000-0.4.1.611.ebuild" -> "ufo2000-0.4.1.622.ebuild")
Created attachment 46736 [details] ufo2000-0.6.627.ebuild Ebuild for the recently released stable version 0.6.627, see http://ufo2000.sourceforge.net So all the previous svn snapshots become obsolete now and svn-ebuild not needed. I hope that somebody will find time to check this ebuild (fix it if needed) and add it to the portage tree.
Hi again, more than one month passed... I understand that there are only three of you responsible for all gentoo game ebuilds. But I frequently visit bugzilla and can provide support in the case of any problems with ufo2000 ebuild. Can you add ebuild for version 0.6.627 to the portage 'as is' with ~x86 keyword? In the case of any problems reported and not resolved by me in a reasonable period of time, you are free to remove it :) I want to remind you that 0.6.627 is a STABLE version that is usually released once per 4-6 months, so having ebuild for it would be nice. PS. I have met at least one gentoo user on ufo2000 server, he tried to use outdated portage version first but then switched to precompiled static linux binary provided on ufo2000 website, who knows, maybe that's a right way to play games and not bother about ebuilds :)
Thanks for the ebuild :)
version bumped. thanks for the ebuild and bug report.
Maybe this is obvious, but shouldn't this latest ebuild (which seems to want subversion) list subversion as a dependancy? Build seems to fail otherwise...
If you have problems with ufo2000-0.6.627.ebuild, can you please post a emerge log to show where it fails? UFO2000 makefile can use subversion for some tasks and also for getting exact version number but it is not strictly requires as far as I know.