Hello, > Could a script using curl and run by cron.weekly (for example) search > source URLs, check whether the downloadable version differs from the > local version, download it if it is, and send a message to the user > that an updated version has been collected?
I use a few such scripts, for example: ----- #!/bin/bash source <(curl -s https://slackbuilds.org/slackbuilds/14.2/system/isdct/isdct.info | grep "VERSION\|HOMEPAGE") cat /usr/doc/isdct-*/isdct.SlackBuild |grep "VERSION=\${VERSION:-$VERSION}" > /dev/null || exit 0 s=$(curl -s "$HOMEPAGE" | grep -c "Version:.*Latest") [ $s -eq 1 ] && exit 0 >&2 echo "New version of isdct, see $HOMEPAGE" ----- or ----- #!/bin/sh s=$(ls /var/log/packages/krop* | grep -c $(curl -s http://arminstraub.com/software/krop | grep -A1000000 "Changelog" | grep -m1 -o "krop [0-9\.]*" | grep -m1 -o "[0-9\.]*")) [ $s -eq 1 ] && exit 0 >&2 echo "New release of krop, see http://arminstraub.com/software/krop"; ----- IMO, better to use cron.daily, because .weekly only delays the information, not reduces the amount of job. Fortunately, in case of sourceforge one can simply subscribe for information on new releases, and in case of github there is rss (which can be checked via rss2email). Best regards, Alexander _______________________________________________ SlackBuilds-users mailing list [email protected] https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
