JediOutcastLinux
JediOutcastLinux copied to clipboard
cpack and TravisCI for packages
Maybe you could add .deb and .rpm files specified with cpack instructions for Ubuntu/Debian and Fedora and than add a .travis.yml which specifies matrices and dependencies and automatically builds the packages.
For example for Fedora you need the dependencies like: mesa-libGL-devel.i686 etc.
Hi!
The problem with packages is, that the executable needs the original Jedi Outcast resources, which I can't package with the Linux executable.
I don't have any logic in place to search for the resources or configure the resource path. Now it is pretty simple - just place it alongside the Windows executable.
With a package, it would install in some directory where you have to copy all the resources into (if you can find the directory). It is still not very user friendly.
If I would invest time to make the installation more easy for everybody, I would want a solution, which just works out of the box. (No copying files around).
And what about just expecting it in a default directory in the home directory? Btw. the executable could still check the current path from where it is started. So if I start it from the Jedi Outcast directory it sould work fine even when the libraries are installed globally on the system.
I still don't like the solution.
I don't see the major benefits of doing it with packaging right now, Of course the dependency stuff would be handled, but I also would get a lot of overhead dealing with packaging, which I'm really not interested in. If I have some time left to do anything on this project, I want to put it in the game and not in the packaging.
The major point for me is, that the packaging would not change much for the end user.
I would consider using packaging if it would make it much easier for the user to handle. I'm talking about installing and running it without moving files or starting the game in a special folder.
So I'm not saying never, but I would want a better way of handling data locations and user communications before I would think about packaging the project. But this is not high on the priority list right now.