Please find attached wolfpack-12.9.12.ebuild Wolfpack is a free, open source, multi-platform server emulator for the MMORPG Ultima Online. It's built using qt and uses python for it's item and npc scripting. I'd suggest games-server/wolfpack
Created attachment 44464 [details] wolfpack-12.9.12.ebuild (New Package)
Comments: No need to depend on tar since that's part of the system. take out the pkg_setup() since it's not needed (and read about how eclasses work) take out the use flags from IUSE that's aren't configurable from the configure script. use unpack ${A} in src_unpack move the chmod +x to src_unpack take out the einfo in src_unpack and src_install There's no way this ebuild gets to make a /usr/games/wolfpack directory - that needs to be changed. Any binaries should go in GAMES_BINDIR and the rest should go in GAMES_DATADIR.
Removed tar as a depend Took out pkg_setup(). I put it there after reading the games.eclass man page, apparently I misunderstood what it was telling me Non-configure script use flags removed from IUSE Used unpack ${A} in src_unpack() Moved chmod +x line to src_unpack einfo's removed Your last point is going to be more difficult. I know where things -should- go, but the binary looks for it's config and script files in the directory it resides in, hence the ebuild makes a new directory. AFAIK, this is unchangeable via make or configure script parameters. I'll ask the wolfpack devs about it, and possibly changing it to a more "normal" linux behaviour. What are the options if that doesn't happen? Thanks for pointing out my errors, this was my first try at an ebuild. I'll attach the revised one after I hear back from the wolfpack dev's.
Created attachment 45327 [details] wolfpack-12.9.12.ebuild Revised ebuild (I didn't add -r1, if I should have, let me know and I'll do so in the future). edited ebuild according to my_bones's requirments. His last requirment, well, see the ebuild to see if it's an acceptable solution. Also fixed a bug I missed first time around, and added a note displayed after merging, about needing to edit a config file before the application will run.
Err, Mr. Bones, not my_bones. BIG sorry, I'm just tired *needs sleep*. Arg and I just made a useless comment.... is there an edit button? :/ I just keep screwing up...
If you can't change the directory via configure, the source needs to be patched to fix the directory. remove the pkg_preinst() function. The permissions need to be set in src_install. What needs to be done to the config file before running? If possible it needs to be patched during the build so the user doesn't have to do anything. If user action still needs to be taken after you've looked at it again, then the pkg_postinst function is the right place, but because you're using the games eclass, you need to call games_pkg_postinst at the beginning of the function. this part of the ebuild still needs to be fixed: sqlite? ( >=dev-python/pysqlite-0.5.1 ) xml2? ( >=dev-python/pyxml-0.8.3 ) !xml2? ( xml? ( >=dev-python/pyxml-0.8.3 ) ) I see no way to select sqlite via configure nor pyxml. They are might be unconditional deps.
Created attachment 45359 [details] wolfpack-12.9.12.ebuild Not sure how easy/hard this will be to do such a patch, but I'll ask. Removed pkg_preinst(), moved contents to src_install() I really doubt it's possible to patch the config so the user doesn't need to do anything. The path to the users Ultima Online install directory needs to be set, so wolfpack knows where to find the client data files (I just realised it doesn't state anywhere that the data files from the official windows UO client are required. Anyone who knows what wolfpack is will know this, but I added it to the description as well). The log file directory needs to be set, the default is ./log, which isn't going to work. Things like server name, what port(s) to listen on, whether or not to enable client encryption, AI settings, what database driver to use (Adding mysql to the configure script only added support, doesn't enable it by default), global respawn settings... the list goes on. Added a call to games_pkg_postinst at the end of pkg_postinst() Your right, sqlite and pyxml aren't used anywhere in the configure script. They were included in response to the linux portion of the install FAQ at http://doc.wpdev.org/FAQ.html#06 Even though the note was specific to debian, I thought it might still apply to other linux distros. I'll ask just to be sure. They can be useful when writing script files for the server, which are done in python. Commented out for now.
No update since 2004. Seems dead to me.
