-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make the .jar file available again along with the other builds #39
Comments
I can no longer make self-contained .jar files as easily as before since UTSU is now a modular project. But I might be able to make it work by writing a second pom.xml file that uses Open-jfx 11 and ignores module files. Then at release time I could use the regular pom.xml for the installers and swap out to the second pom.xml file just for the .jar file. Another thing I could do is release a .rpm installer for Linux as well as a .deb installer. This would actually be much easier than releasing another .jar. |
Lethe, I was thinking about it since I found out that you released the new version and, as a Linux user who is not a builder, I suggest you to use the AppImage format, it is the most used and practical Universal Linux Format that exists until the time. I have seen several cases of people preferring to use programs in this format than downloading them directly from their distros' own repositories. I believe that it would calmly solve the problem of users with different distros in the penguin world ... |
For more information: https://pt.wikipedia.org/wiki/AppImage Git Hub |
I agree, an AppImage would be a good idea. |
Don't have an AppImage yet, but in the latest release (0.4.3) I packaged a raw Linux executable into a Zip file and added a README with instructions for running on the command line. |
I hope it works, I have trauma from the previous installation method ... lol |
This would make it easier for people who don't use Debian based distros to run the software. It might even help people trying to install UTSU on a Raspberry Pi.
The text was updated successfully, but these errors were encountered: