Since I never had the need to keep older versions alive, apart from step 1 my install and upgrade procedure are the same:
1: mkdir ~/Programs/basex 2: Download BaseX.zip 3: Unzip to ~/Programs
I never needed to (re)create the data directory or the symbolic link After adding ~/Programs/basex/bin: to my path, I can start basexgui or basexserver & from the coammandline.
Ben
Op 17-03-2021 om 20:26 schreef Graydon:
On Wed, Mar 17, 2021 at 03:05:58PM -0400, Bridger Dyson-Smith scripsit:
Per the recent thread about installing, I was hoping to convince some of you to share your experiences installing and running BaseX. Whether you use Mac OS, Windows, a Linux, or something else: how are you installing and running BaseX?
This is on Fedora; it's pretty much strictly an update process by now, though the install process only skips step 3.
- Download BaseX.zip from the website into ~/bin/basex
- cd ~/bin/basex
- mv basex BaseX$VERSION
- unzip BaseX$VERSION.zip
- cd basex
- rmdir data
- ln -s ../data .
Because the executables are always on the same path -- ~/bin/basex/basex/bin -- I don't have to update the shortcut icons when I update versions.
Every now and again I'll go through and prune old versions from bin/basex.
It would be _better_ if there was a Fedora package and I didn't have to think about performing the update, but, well, BaseX is on a very short list of software that's useful enough to use even if it's not available as a Fedora RPM via dnf.