Due to the lack of a few files from outside the actual game install directory, mods will be unable to find the game and will fail to install. The directory is /root/.loki and there should be xml files in it pointing to the installation. I'll research further on this, but wanted to post a bug to remind myself.
doesnt it looke at ${HOME} ? thus can we add something to the eclass to (1) set HOME=$T and (2) autogen bogus .xml files in $T that point at our /opt/ut2003 ?
Actually, I'm not really sure how it works. I'm going to have to go through a real install to find out. This is also an issue with ut2004, so I want to get it fixed before I put it in portage.
Created attachment 30290 [details] ut2003-2225-r3.ebuild This is a new ebuild which should work to provide mod support. Please test this and report back to me.
Created attachment 30291 [details] files/ut2003.xml You will also need this file to be in ${FILESDIR} before trying to merge this ebuild.
I guess this may or may not work... I really need to go back and revisit this bug...
This feature of Loki installers is really a *good* thing to ignore, because: It encourages users to install via ebuilds (ideally with collision protection turned on), so they can see if they would be overwriting any of Unreal Tournament's own files. Installing previous versions of some of its files will make UT200x crash in impossible-to-debug ways, and re-installing all of UT200x (especially if it's on 6 CDs) isn't attractive. Manual installations belong in /usr/local rather than /opt, anyway. The eclass in bug #121647 will make writing ebuilds for these games even easier.
