scripts/bash/deb-update.bash

#!/usr/bin/env bash

# A simple script for updating all package managers simultaneously

# Show commands being executed
set -x

#export LANG=C.utf8
# This is said to be a poor practice that should only be used for debugging
export LC_ALL=C.utf8

# if hash checks that the command exists
if hash apt-get 2>/dev/null; then
	# I am not sure if -y here even does anything, at least it won't work for
	# accepting suite changes for Debian when testing becomes stable.
	# Checking for updates or new packages.
	apt-get -y update

	# potentially unsafe first time, so there hopefully is space for new kernels
	apt-get "$@" autoremove

	# If arguments like -y are passed to the script, they become "$@"
	apt-get "$@" upgrade --with-new-pkgs

	# potentially unsafe, second time after new kernel is installed
	apt-get "$@" autoremove
fi

if hash dpkg 2>/dev/null; then
	# In case dpkg was interrupted previously, configure packages.
	dpkg --configure -a
fi

# Enables Fedora third party repositories if not enabled, otherwise quiet.
# My systems most likely have them already
if hash fedora-third-party 2>/dev/null; then
	fedora-third-party enable
	# Are they enabled?
	fedora-third-party query
fi

if hash dnf 2>/dev/null; then
	# I don't know if -y does anything here either and I think this may be
	# useless, but I am used to it coming from apt and I think it will just
	# say nothing to do or do nothing if mirrors haven't updated.
	dnf -v check-update -y

	# potentially unsafe first time, I am not sure if this is concern outside of Debian/Ubuntu though
	dnf -v "$@" autoremove

	# If arguments like -y are passed to the script, they become "$@"
	dnf -v "$@" upgrade

	# potentially unsafe, see a few lines above and the apt-get section
	dnf -v "$@" autoremove
fi

if hash rpmconf 2>/dev/null; then
	# Tests if there are rpmsave/rpmnew files, hopefully is non-interactive
	rpmconf -a -t
fi

if hash flatpak 2>/dev/null; then
	# Flatpak apps are sandboxed and should be safe to update automatically
	# KEEP --noninteractive IN PLACE! While it removes progress bar, it also
	# doesn't blink making it worth it in case of migraine attack.
	flatpak update --noninteractive --assumeyes
	flatpak update --noninteractive --assumeyes --no-static-deltas
	# Note to self
	echo '!!! In case of weird errors e.g. while trying to checkout, try running: flatpak repair'
	#echo '	  404 is not a weird error, try flatpak <subcommand> --no-static-deltas'
	# Flatpak's version of `apt autoremove`
	flatpak uninstall --unused --assumeyes --noninteractive
	# And as an user although probably inapplicable for sudo/root
	flatpak update --user --noninteractive --assumeyes
	flatpak update --user --noninteractive --assumeyes --no-static-deltas
	flatpak uninstall --user --unused --assumeyes --noninteractive
fi

if hash snap 2>/dev/null; then
	# Snap packages auto-update anyway though, but I like checking them while
	# doing everything else too
	snap refresh
	# so I may have some sort of an idea when snap packages have been updated
	# if they have auto-refreshed
	snap changes
fi
# I don't have flatpak or snap going to background, because I often do
# ./deb-update.bash && poweroff

if hash pkcon 2>/dev/null; then
	# So PackageKit using KDE Plasma and possibly GNOME stop alerting about
	# already installed updates. It has backends for all other package managers,
	# so it needs to be after them.
	pkcon refresh force
fi

if hash apt-file 2>/dev/null; then
	# So the local apt-file database is up-to-date.
	apt-file update
fi

if hash needrestart 2>/dev/null; then
	# needrestart batch mode, should be visible on bottom of scrollback
	# see https://github.com/liske/needrestart/blob/master/README.batch.md
	needrestart -b
fi

# Sedric workaround, located in this repo. I trust /root/
if [ -f /root/fixgrub.bash ]; then
	/root/fixgrub.bash
fi

# Hide commands being executed again
set +x