Sudo access required for app and theme instalation

[nukusaba]

When installing urn its binary gets stored in /usr/local/bin/ and the .desktop in /usr/local/share/applications/. it'd be more optimal to store these in user-level space, ~/.local/bin/ for the binary, and ~/.local/share/applications/ for the .desktop file.
The application itself isnt likely going to be reinstalled a whole lot, so its not the biggest issue. however it also affects themes, which are meant to be installed and switched between without much restrictivness. Storing themes in ~/.local/share/urn/themes/ would be more intuitive since it doesnt require root access, and users would be more likely to figure out that path than /usr/local/share/urn/themes/

[miKa-pyon]

I use multiple users and would prefer to keep the paths the way they are. I can not see why one would want to manage the same binaries over several user paths.
For a single-user, local install, is it not enough to edit the PREFIX variable in the Makefile?

Edit: Removed comment about themes. I forgot how themes work but they are fine as it is.

[nukusaba]

the executable itself could stay where it is. maybe a arg for user-specific install if wanted by the user, so you dont have to manualy change stuff in the make file would be useful tho.

for themes it'd be good to have them as both user-specific and system wide i'd say. having them user-specific is gonna make theme creation and testing easier and faster, while you could still install themes in root if you want them systemwide.

[miKa-pyon]

Have an option, yes! ♡
It might be an improvement in general if the PREFIX variable in the Makefile would support DESTDIR?
We could then use make DESTDIR=/my/custom/path/?

I tried making a template for Void Linux and had to patch in the DESTDIR for the packaging step (among other things).
Similarly, the Arch Linux template skips the make install step(?) and recreates it manually instead, probably for the same reason?

My wording is bad. I have no preference with the themes issue either way.