Can games-strategy/warzone2100 be marked ~amd64 in portage? Reproducible: Always Steps to Reproduce:
warzone2100-2.0* is definitely NOT 64bit safe. Hence the forced -m32 in configure.ac. Our trunk runs on x86_64, but is still not considered safe, as there are a few issues left. The patches were too many and too fuzzy to be ported back. Before warzone2100-2.1 I can't recommend ~amd64.
So we will mark a later version.
*** Bug 184197 has been marked as a duplicate of this bug. ***
*** Bug 191931 has been marked as a duplicate of this bug. ***
Created attachment 137347 [details] warzone2100 svn ebuild I hacked up an svn-ebuild for my own personal use half a year ago, since the 2.0-branch does not work on amd64. (2.1 will work, though) It proved quite fine for me and wz can be considered almost stable for some quick skirmishes; upstream is making good progress on it.
Thanks. :) Some notes on dependencies: JPEG and MP3 support are gone. media-libs/libvorbis should always depend on media-libs/libogg (which should thus not need to be specified explicitly). Version 1.1 required. NLS is supported (sys-devel/gettext >=0.15 required). sys-devel/flex (>=2.4.2) and sys-devel/bison (>=1.31) are required to build. As well as sys-devel/automake 1.8 and sys-devel/autoconf 2.56. dev-util/pkgconfig-0.9 (guessed by what their config checks...) media-libs/libpng should be >=1.2, as well as media-libs/libsdl and media-libs/sdl-net. dev-libs/popt required (1.10 works, haven't tested below). dev-games/physfs needs to be >=1.0.1 (1.0.0 is buggy). Some of these are "system", devmanual says not to specifiy them unless a specific version is required. So this would probably apply to popt, where it is not known which version is exactly required.
Created attachment 137369 [details] Variant of the svn ebuild - untested This is a variant of MB's ebuild by me, please decide whether the explicit DEPEND is correct this way.
Created attachment 137485 [details] Added a small check for opengl-activation I basically took Dennis' version and added a small check for activated opengl with SDL. A note to the required build-dependencies: All the requirements for bison, flex, autoconf and automake are in the system target. Every ebuild implies this dependency. Since the mentioned versions are ridiculously outdated (flex, bison) and/or explicitely checked at compile-time I think it's sure to leave them out.
Created attachment 137651 [details] added desktop/icon installation
Created attachment 137660 [details] made a few minor changes due to Mr_Bones_' request
Can you maybe list the changes since the last version of the ebuild? Patch in the comment, maybe? Since I have no idea what the "few minor changes" were. Icon installation didn't work? Then that's a bug... Will try to hunt it down.
Created attachment 137746 [details] Some more changes. Undid manual .desktop install. Mostly cosmetic. Also for the depending quesoglc-dependency, check http://bugs.gentoo.org/show_bug.cgi?id=195096
Created attachment 137748 [details, diff] diff of attachment 137485 [details] to the latest (137746) for control purposes
I am not sure whether libintl alone is enough for building, as you also need the gettext binaries, like xgettext and msgfmt, etc. to build the .po files.
Libintl is in RDEPEND, which means for runtime it is required. DEPEND controls build-time dependencies. It contains all runtime dependencies and additionally gettext is required.
Disgraced myself... Will look more thoroughly next time.
This looks like its been quite stagnant for awhile. Is this still being worked on upstream or is the ebuild outdated on amd64? Apologies if this is incorrect. Seems to compile fine on amd64 albeit not in portage.
Nope, we are not yet dead. ;) And games-strategy/warzone2100-2.1_beta4 is in ~unstable for all supported arches at the moment, thus also for amd64.
Can't seem to get portage to let me have it. Trying emerge =games-strategy/warzone2100-2.1_beta4 with both ~amd64 and ** keywords... Seems like something is quirky. Just me? Apologies as I am new to the whole ebuild thing. Never really had time to toy around with it before.
I kindly ask you to rtfm. warzone2100 is masked by package.mask ([M]) and unstable keyword (~). Hence, add "warzone2100" to your package.unmask and warzone2100 to your package.keywords. This way, *all* warzone2100 versions will be unmasked, except those missing your arch's keyword.
Created attachment 195021 [details] New repository, some other changes. Warzone has moved to a new repository. This is a modification of 137746 attachment.
Created attachment 205125 [details] Ported to EAPI2
.
taking amd64@g.o off this bug, it is an old issue and the ebuild has "~amd64" already. I suggest opening a new bug for changes to the ebuild.
Fixed.
