rautamiekka
commented
6 years ago RPM/DEB can package the JAR and create dependencies.
The symlink approach creates a little of a confusion.
Open cyian-1756 opened 6 years ago
rautamiekka
commented
6 years ago RPM/DEB can package the JAR and create dependencies.
The symlink approach creates a little of a confusion.
Currently ripme is distributed as a jar file that users are expected to just put where ever and run, this approach has some issues with it
Ripme can't be included in most linux software repositories as these repositories require the program to be packaged as a rpm or deb installer.
Ripme won't get a menu entry unless the user manually creates it
If a user doesn't have java installed they'd have to manually install it whereas both deb and rpm installers give the option to list java as a dependency, meaning that it would be installed automatically
The only issue I can see here would be that installing ripme straight into /usr/bin or the like would break ripmes updater as only only root can write to those directories. This problem could be dealt with by install ripme to ~/.local/bin and putting a system link to it in /usr/bin