[chbot] Updating a program: which Way did I use to install it?

[Andy Gardner]

Egads, what a dog's breakfast.

Quick, install Wordpress on the system and that'll make your mess pale in comparison.

On 25/08/20 12:16 pm, Stephen Irons wrote:
> It is worse than I thought. Here are the ways that programs are installed on my PC:
> 
> * Debian packages installed from official repositories
> * Debian packages installed from numerous PPA repositories
> * Snap installs from some Snap store -- is there more than one?
> * AppImages downloaded from arbitrary websites, and manually moved to either ~/bin
> * AppImages downloaded from arbitrary websites, and somehow ended up in ~/.local/bin
> * Flatpack installed from flathub
> * Flatpack installed from the applications' private flat-stores
> * Python packages installed using 'pip', from py-pi
> * Python packages installed using 'pip' from some other Python package place
> * Source code tar file downloaded from the applications' website, then built manually 'configure; make; sudo make install', ending up in /usr/local
> * Source code version control repository cloned, then built manually 'configure; make; sudo make install', ending up in /usr/local
> * Tar file with precompile binaries downloaded, unpacked (usually into /opt) then created symlink in '~/bin'
> * Single precompiled binary downloaded from some website, then moved to '~/bin'
> * Personal scripts in '~/bin' to set-up before and tear-down after some other program (eg. always pass specific arguments, to run pasuspender, or to set environment variables), or just to give it a nicer name. These are version controlled.
> * Command interpreter aliases used for the same purpose. I prefer one-line scripts in '~/bin' as they can be version controlled.
> 
> Note: after downloading stuff from random web sites, I usually remember to compare the hash before using it. This does assume that I trust that web site...
>