Request to include the ebuild for the full version of Majesty Gold, as ported to Linux by LGP, into the Portage tree. Reproducible: Always Steps to Reproduce:
Created attachment 52081 [details] Proposed ebuild This ebuild based on the one introduced into the tree recently for Majesty demo. Version 1.4.0 is the one reported by the game when it's ran.
Correction: 'majesty' binary (used to start the original game) gives version number 1.4.0, while 'majx' (used to start original game w/expansion) reports 1.1.0. Not sure which one is appropriate for the ebuild. There were no additional patches for the game, nor they are likely to appear, so perhaps 1.0.0 (like the demo) would do just fine.
Just a side note: LGP does actually plan on releasing a patch... when they're done with it... eventually.
When is it going to be in portage?
http://www.gentoo.org/proj/en/desktop/games/#doc_chap5_sect10
Created attachment 90070 [details] majesty-1.1.0.ebuild Hi, I *finally* tested this ebuild. Looked ok, however I updated a couple of things. First, I added a line to install the libopenplay library from the majesty CD. It is installed in the subdirectory of the game install area, and is expected for multiplayer to work. Second, I commented out the lines which install majesty (leaving only majx). I did this because all missions are available in majx (The original and the expansion), but if one runs majesty (instead of majx) only the original missions are available. That and the status of the completed games is not transfered from majesty to majx without some tricky save file hacking. Otherwise everything appeared to work fine. I didn't detect that any other dependencies are necessary at this time. Chris, I'm not sure if you have this game, so I'm not sure what else would be necessary to get this into portage. One other note. The majesty-demo lives in games-strategy. I'm wondering if this new ebuild should live in games-simulation as it is a "Fantasy Kingdom Sim". Either way is better. Thanks all.
Comment on attachment 90070 [details] majesty-1.1.0.ebuild Given that I suggest only installing majx, I also suggest that this be marked as a 1.1.0 release.
(In reply to comment #6) Wouldn't it be better to keep the game installation intact? Windows version of Majesty Gold also installs both the original game and the expansion, and even creates shortcuts for both. I'm not sure what is the purpose of that (though a wild guess would be that you'd need the original client to play multiplayer games with people who do not have the expansion), but I think that either way it's something for upstream to decide upon, not us.
Yep. I don't mind if one or both game entrypoints are provided. I suggested to include only majx (majesty + the northern expansion) because your quests completed in majesty are not remembered when you try to start the northern expansion. That is you start majx (after completeing majesty) and *none* of the quests are completed, because what you complete in majesty is viewed by the game/s as different then what you complete in majx. My point is derived from personal anguish as I "learned" about this "feature" the hard way. I'm only trying to help others from experiencing the same anguish. So either way. Whatever consensus is. I don't mind because I've already learned and can avoid reliving the past. Thanks.
Please remove virtual/x11 from RDEPEND, and add media-libs/sdl-mixer to it. Maybe another SDL libs are needed.
Created attachment 213783 [details] Updated version with latest patches I hacked up an updated Majesty ebuild that uses the patches available from LGP to give the most recent version. I installed both the majesty and majx binaries, as the original majesty binary is required for one of the two quests included in the patches. Play-tested (but not extensively) on amd64 and x86. The patch files do not seem to be available for ppc, so I removed the PPC sections from the ebuild. I guess that before merging this ebuild probably needs a little bit of tidying (I am happy to update it if anyone has comments) and addition of the license to portage. It would also be possible to install either hi-res movies, low-res movies or none at all, and not install the music, to cut down on the installed size.
Created attachment 215851 [details] Updated ebuild for majesty 1.4.03 This ebuild adds some things missing from the earlier one, such as being able to toggle installation of music with a USE flag, a EULA check, the ‘interactive’ property, installation of documenation and some other tidying. The EULA is required for the license check, attaching next.
Created attachment 215853 [details] EULA for majesty The EULA is required for the license check of the updated 1.4.03 ebuild. Anything else before the ebuild can be added to portage?
