The zip package from (currently) https://files.basex.org/releases/12.0/BaseX120.zip unpacks and you're basically done. (With the caveat of needing an appropriate Java installed.)
Mine lives in $HOME/bin/basex, so the actual executables are $HOME/bing/basex/basex/bin because there's a variety of versions: 12:32 basex % ls basex/ BaseX116.zip basex-118/ basex-119last/ custom/ BaseX114.zip basex-117/ BaseX118.zip BaseX119.zip data/ basex-116/ BaseX117.zip basex-119/ BaseX120.zip old/ The only thing that changes is that in the current basex/ the data/ directory (where all the db content lives) becomes a sym link up to $HOME/bin/basex/data so the active databases carry over at upgrade time. I would not expect this to be any more challenging on Debian than it is on Fedora. And yes, it'd be nice if it was a package, but on the other hand the data isn't global and the data lives with the rest of BaseX so I find this works well. -- Graydon On Wed, Jul 23, 2025, at 12:06, Rory Campbell-Lange wrote: > Dear List > > I may be working soon on a commercial server supporting XQuery 3.1+ with its > own proprietary extensions, and XSLT 2.0. > > Would basex 12 be the best match for these protocol versions (except of the > proprietary components, of course)? I'm most interesting in working in an > iterative fashion on the command line, as I'm used to doing with vim and psql > (the postgresql interactive terminal). > > If basex 12 is recommended, any pointers to getting this running on Debian > would be gratefully received. Unfortunately Debian testing > (https://packages.debian.org/sid/basex) still points to basex 10.5. I'm not > familiar with Java installation requirements. > > Thank you for the project, which looks excellent. > > Many thanks, > Rory >
