@bronze Regarding the JDK issue, I feel uncomfortable removing the version requirement. I think the best approach would be to add versions to the provides
of the jdk
package such that the version criteria are fulfilled for this package. What do you think?
Concerning the Minecraft server management script, yes it indeed has been moved to its own repository. However, all the configuration is done during "build" time. To be specific, make
configures everything. See the corresponding Makefile. Because it currently needs to be adapted to a specific server at build time, it does not make sense to package it on its own in a separate package.
The script really is just a small management script and IMHO it is not worth making some kind of pluggable library out of it that could be depended on. If you have an idea of how to provide a sensible management script package, I am happy to create and maintain it.
EDIT: In case you just want a dirty hack to not install the server but everything else, simply set /srv/minecraft to be ignored during installation by pacman, see https://wiki.archlinux.org/title/Pacman#Skip_files_from_being_installed_to_system .
Pinned Comments
edh commented on 2016-06-18 18:24 (UTC) (edited on 2021-10-02 08:19 (UTC) by edh)
To get an overview of the available options provided by the management script, be sure to have a look at the help page or read the according section on the ArchWiki article [1].
You can quit the console without shutting down the server by press ctrl+a d (first ctrl+a and after releasing the buttons press d; ctrl+b also works). This will detach your input from the server console. The attaching and detaching is done with tmux (previously GNU screen) since it lets you view and type into the console, send single commands to it and keep it alive without a connected user. Take a look at the the command overview at the ArchWiki [2] to get a feel for its power. (@carmelo12341)
[1] https://wiki.archlinux.org/title/Minecraft#Setup [2] https://wiki.archlinux.org/title/Tmux