For some AUR maintainers could be really useful add custom scripts to check new releases within the same plasmoid, to know when they should upgrade their AUR packages.
Example scenario: a script to check new Google Chrome Beta releases:
#!/bin/bash -eu
INSTALLED_VERSION=$(pacman -Qi google-chrome-beta | awk '/^Version/ {print $3}' | sed 's/-/\n/g' | head -1)
LATEST_BETA=$(
curl -sL https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/other.xml.gz | \
gzip -df | tr ' ' '\n' | grep -e name= -e ver= | cut -d '"' -f2 | sed 'N;s/\n/ /' | \
grep google-chrome-beta | awk '{print $2}'
)
if [[ "$INSTALLED_VERSION" != "$LATEST_BETA" ]]
then
echo "new google-chrome-beta available $LATEST_BETA"
fi
To store this scripts I think something like nnn where you can install your custom scripts in $XDG_CONFIG_HOME/nnn/plugins
and maybe the user can switch ON/OFF the google-chrome-beta.sh in the Arch updater settings
Obviously this feature could be used for any kind of notification that the user wants to receive in this plasmoid.
For some AUR maintainers could be really useful add custom scripts to check new releases within the same plasmoid, to know when they should upgrade their AUR packages.
Example scenario: a script to check new Google Chrome Beta releases:
To store this scripts I think something like
nnn
where you can install your custom scripts in$XDG_CONFIG_HOME/nnn/plugins
and maybe the user can switch ON/OFF thegoogle-chrome-beta.sh
in the Arch updater settingsObviously this feature could be used for any kind of notification that the user wants to receive in this plasmoid.