This! A .bin file - not stuck to a Snap (which is a turd) or .Deb - lots of people don't run Debian (or MS (err Canonical) Ubuntu).Quote:
Okay my $.02 having 30 years of UNIX and UNIX like programming and administration. The installer should be a a .bin file; Which in UNIX land is a self extracting shell installer. Way too many different package managers out there to try and support one or 22 of them. There are copious examples on the web for how to create these most of them are for Bash which would be fine since you're only making a LINUX port. The FGU base program and everything need to launch should install under the /opt or /usr/local hierarchy. /opt most likely since again this is LINUX. (don't get me started on that). Trying to keep up with some package management system is just a waste of cycles IMO and this would give us the most flexibility how/where we (the guys running the systems) want it installed.
Once the program is launched by the user all configuration files and any downloaded content should be stored to ${HOME}/.fantasygrounds <-or whatever as long as its identifiable. All you folks going crazy about wanting it under a .local
tree so you home dir is pretty should just go back to Windows IMO :) Okay I'm 75% kidding a (.local|.config|.whatever) is fine by me as long as I can find it easy.
So like everyone else the real problem I see is the part of the updater that updates FGU itself. The in-app updater should update all the downloadable content just fine. But FGU binaries should only be updated by a privileged user and for the love of all that's holy don't try and do this yourselves. Way to many professional full time UNIX programmers screw that up. I don't need a big old hole in system security due to my gaming table software.
Personally I'm 100% okay with a notice when I hit update telling me I need to run `sudo ${HOME}/.whatever_linux_insanity_is_choosen/FGU_UPDATE-{verx.y.z}.bin` from a terminal and then rerun the in-app updater. Might seem clunky to SmiteWorks and people coming from Windows but LINUX guys aren't going to be too put out by that. Especially since it allows us to keep running our systems the way we want.
-OR-
Just put the whole thing under ${HOME}/someplace owned by the user. Sure this is sorta crappy from a LINUX point of view but I already have several games that will only install that way so... And are you really going to run multiple VTT as different users at the same time? And even if you do. Just install it again as the other user disk is cheap.