Debian install - System or Appimage

English
#1

Looking for some brief input on package options: I am running Debian and installed LO a while ago I noticed the Debian repo does not have he most up to date I think it is running 7.0.4.2. I found the Appimage Still version 7.3. I do not need bleeding edge but I think 7.0 is 24 months out of date currently looking at the archive index (Jan 2021 release.) I don’t mind manually updating programs but it looks like my 7.0 does not have a check for updates option (either manual or automatic) anywhere I can find. Therefore I would need to watch the rss feed for updates and manually download the latest deb file. This is not a problem but given it is not going thru Debian testing I suppose there is always a risk of incompatibility and having to do a rollback with a system snapshot. Alternatively I can just run the Appimage and be done with it. I noticed the Appimage version has the online update setting inside the options setup, it also has check for updates in the help menu as well as the check updates gear wheel in the top right corner of the app. Two questions; 1 - Any significant pros or cons with me running the full install with manual updates as described above vs just using the Appimage going forward, or is it just a difference of convenience at this point? 2 - I noticed that my Appimage install is pulling toolbar settings, installed extensions, and templates that are already part of 7.0, into the 7.3 Appimage - does this mean the Appimage is sharing data in the .config/LO directory? I thought the basic idea of Appimage is to be self-contained, so if it is storing operating files outside of the appimage file (which I have in the my documents directory) how does this come into play with system backups and restore do I need the .config/LO directory to properly bu and restore all of my settings to operate the LO Appimage? Cofused on how this works.

Thanks in advance

As a follow-up question related to #2 above - If I stay with Appimage and do a full purge removal of LO in the repo will this cause me to lose my settings and templates in the Appimage since they appear to be sharing directories in the .config?

#3

An appimage/snap etc. is self-contained in concern nit to need much from your OS and therefore brings libraries, wich are already on your system, and can use own versions of libraries.
.
But an AppImage/snap etc can store and use files outside the container. This starts with the files you create, when you save a File to your $HOME but includes also hidden config-files/folders. Note: This is usually allowed through a manifest-file for the container. It is possible for maintainers to deny any access to local files, or allow more than your $HOME.

IMHO three main points for me concerning LibreOffice.

  • Check, if your container is complete. For example Ubuntu ships LibreOffice without Java and the database component Base. For a regular install you may change this via apt, an appimage you use as-it-comes.
  • Restricted access to your system is a feature concerning security, but can be an obstacle, when one tried to use system-commands via Shell() in macros.
  • Auto-update implies(?) you always get the latest version. I’ve seen no option to downgrade, if a version’s bugs make LibreOffice unusuable for you. But maybe I just missed the archive for older versions.

In general: Debian is a very “stable” distribution, wich rarely updates applications. So you usually have to use/add another repository, if you want more current versions - as already suggested by @erAck

Keep copies of the User-Profile as backup, even if they are usually not lost during upgrades.

#5

Thanks for details that is helpful.

#2

If on bullseye you want to add the bullseye-backports repository to your /etc/apt/sources.list like this:

deb http://deb.debian.org/debian/ bullseye-backports main contrib non-free

That currently has LibreOffice 7.4.3, see Debian -- Details of package libreoffice in bullseye-backports .

#4

I didnt know that. I avoid backports I prefer reliability but I’ll consider that as an option here thanks.

Impressum (Legal Info) | Datenschutzerklärung (Privacy Policy)   Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.