deb-update.bash: there isn't that much impact in caching as it will see cache is recent enough

This commit is contained in:
Aminda Suomalainen 2024-04-27 21:22:31 +03:00
parent 585478af97
commit b126d56667
Signed by: Mikaela
SSH Key Fingerprint: SHA256:CXLULpqNBdUKB6E6fLA1b/4SzG0HvKD19PbIePU175Q

View File

@ -43,7 +43,7 @@ if hash dnf 2>/dev/null; then
# I don't know if -y does anything here either and I think this may be # 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 # 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. # say nothing to do or do nothing if mirrors haven't updated.
#dnf -v check-update -y dnf -v check-update -y
# potentially unsafe first time, I am not sure if this is concern outside of Debian/Ubuntu though # potentially unsafe first time, I am not sure if this is concern outside of Debian/Ubuntu though
dnf -v "$@" autoremove dnf -v "$@" autoremove
@ -51,9 +51,8 @@ if hash dnf 2>/dev/null; then
# If arguments like -y are passed to the script, they become "$@" # If arguments like -y are passed to the script, they become "$@"
#dnf -v "$@" upgrade #dnf -v "$@" upgrade
# check-update and upgrade together, causes more traffic due to less # Doing check-update and upgrade together seems to be necessary for
# caching, but required for certain Chromium-based browsers with their # Chromium based browsers and their repositories :shrug:
# own repositories
dnf -v "$@" upgrade --refresh dnf -v "$@" upgrade --refresh
# potentially unsafe, see a few lines above and the apt-get section # potentially unsafe, see a few lines above and the apt-get section