Hi, Christian, I am not qualified to speak about these things, being a Windows user and without a clue concerning all those Unix things. My naive perspective is this: as a Windows user, everything is wonderfully simple - download the installer, click, click, click. done. But with Unix, it seems that it's not quite so, and perhaps even Hackerish knowledge comes into play, and ease may hinge on levels of expertise and experience. And I think it is worth the effort to have a beautiful documentation of installation and upgrade, extending all knowledge, know-how and what-not on a silver tray.

Am Mittwoch, 17. März 2021, 18:52:36 MEZ hat Christian Grün <christian.gruen@gmail.com> Folgendes geschrieben:


Hi Hans-Jürgen,

Should this perhaps be part of the official documentation? Especially installation and upgrade deserve maximum attention and helpfulness.

I certainly agree. Suggestions are always welcome, either via this list or as directed edits in our Wiki. I hoped that the existing information on how to install BaseX is self-explanatory enough, but maybe we should add more details? Or are you specifically missing hints on how to update certain distributions (such as the ZIP distribution)?

Viele Grüße
Christian



Am Mittwoch, 17. März 2021, 18:07:38 MEZ hat Bridger Dyson-Smith <bdysonsmith@gmail.com> Folgendes geschrieben:


Hi Joris,

On Wed, Mar 17, 2021 at 5:39 AM commandline-be <commandline@protonmail.com> wrote:
ok, thanks.


If i can i will try and figure out an upgrade approach or see if i can run a backport which does have the more recent version available.

I've found that something like this following works very well for me across several operating systems:

```
cd ~/bin
mkdir basex-src basex-data
unzip BaseX.zip
rm -rf basex/src basex/data
ln -s ~/bin/basex-src ~/bin/basex/src; ln -s ~/bin/basex-data ~/bin/basex-data
```
You can include the ~/bin/basex directory path in your environmental $PATH and you're off to the races.

Subsequent updates are basically grabbing the ZIP archive, unpacking it, removing the default src and data directories, and recreating the symbolic links.
All of your database info is kept separately from the defaults, so you don't worry about overwriting in an upgrade.

It's still manual and necessitates some steps, but it's been an easy method for me across several different unix-like operating systems (Redhat, Void, and FreeBSD) that don't have a package for installation.

I know some other people have posted similar approaches here on the mailing list, but I can't think of an easy search term to help locate them.
 
Essentialy, i dislike Ubuntu a lot and Arch well, i never got round to arch really.

Best,

Joris

HTH
Best,
Bridger

 

- - -
mailto:commandline@protonmail.com

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, 17 March 2021 10:35, Christian Grün <christian.gruen@gmail.com> wrote:

> > Linux is eays, everything is a file. It are the specifics which make it hard, particularly configuration.
>

> Right. At the moment, there is no automatized process to get the
> Debian/Ubuntu distribution updates automatized.
>

> > I think my issue with the Preferences panel may come from running the most recent basex and it overwriting configuration files since it writes a message to screen saying it overwrites the configuration file.
>

> Thanks for the insight. If you want to stick with the old version of
> BaseX, you can delete the .basexgui file (which includes the GUI
> configuration) to resolve the issue.