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.

1. Download BaseX.zip from the website into ~/bin/basex 2. cd ~/bin/basex 3. mv basex BaseX$VERSION 4. unzip BaseX$VERSION.zip 5. cd basex 6. rmdir data 7. 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.

Just like you, I usually download the Zip package on Windows and Linux. Then I put a Saxon Jar and maybe a Saxon license file in the lib/custom directory and adjust Xmx in the startup scripts for the given platform.

So I don’t use package managers for BaseX.

For some projects, I add BaseX and Saxon to the project’s (svn) code repo. I populate the webapp directory with project-specific code. If a new BaseX release arrives, I unzip it over the existing files, inspect the changes to the scripts in bin/ and to webapp/WEB-INF/web.xml, reverting the changes to these files most of the time so that my project-specific changes are preserved. I don’t do this for each and every new release. One project that I’m working on is still on 9.3.2 beta.

Another (public) repo version that I use as an XSLT service when deployed (instead of a Saxon servlet) currently runs 9.4.6: https://subversion.le-tex.de/common/basex It is bundled with Saxon PE 10.3 (not with a license file though), with a sample XSLT that transforms factbook.xml (https://subversion.le-tex.de/common/basex/etc/factbook.xsl) and with additional documentation (https://subversion.le-tex.de/common/basex/readme_modifications.txt)

Gerrit

On 17.03.2021 20:05, Bridger Dyson-Smith wrote:

Hi all -

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?

I'm asking as there could be some possible improvements to the wiki that might help new users (or even less-new users!) get up and running.

Thanks in advance for your time and trouble! If I can hear about number of approaches, I'm happy to attempt writing up some details for the wiki. Best, Bridger

PS Here's mine:

Operating systems: I'm typically using BaseX on either a FreeBSD or a Void Linux system (rarely on other Linuxes, and only once or twice on Windows).

Install process: my OS' don't have a pre-packaged download for BaseX, so I do something like:

1. cd ~/bin
2. mkdir basex-src basex-data
3. fetch|wget https://files.basex.org/releases/BaseX.zip

https://files.basex.org/releases/BaseX.zip 4. unzip BaseX.zip 5. rm -rf basex/src basex/data 6. ln -s ~/bin/basex-src ~/bin/basex/src; ln -s ~/bin/basex-data ~/bin/basex/data ... 7. enjoy basex!

Upgrade process: something like

1. cd ~/bin
2. fetch|wget https://files.basex.org/releases/BaseX.zip

https://files.basex.org/releases/BaseX.zip 3. mv basex basex-old 4. unzip BaseX.zip 5. rm -rf basex/src basex/data 6. ln -s ~/bin/basex-src ~/bin/basex/src; ln -s ~/bin/basex-data ~/bin/basex/data ...

Usage note: I have a line in my shell RC file (~/.zshrc) that helps my shell/command line know where to find the various basex executables: `export PATH="$PATH:$HOME/bin/basex/bin"`