SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Below follows a script code I wrote to check for Slackware changelog changes.
It will display only the changed parts of the changelog (since the last time the script has been run).
IMHO, I would consider also the -N option of wget, that downloads a file only if the timestamp is different from the one of the local copy (to be friendly versus the server hosting the changelog): note that this can't be used in combination with -O (see the man page) so if you decide to use it you might have to change the script a little...
Below follows a script code I wrote to check for Slackware changelog changes.
It will display only the changed parts of the changelog (since the last time the script has been run).
I changed it slightly so there's no output in case the changelog doesn't change (maybe useful for putting it in crontab so you get a mail only if it changes)
Unfortunately this is no longer the truth
I spent some time and boiled something more complex
Quote from README:
Quote:
slackchlog is Slackware's ChangeLog viewer written in BASH.
It allows to download and view the remote ChangeLog file and
also to generate RSS feed suitable for RSS feed readers.
Using command line arguments, it's possible to specify
the architecture, release and mirror for the ChangeLog file
in question.
For usage details, type:
$ slackchlog --help
Help output:
Code:
Usage: /usr/bin/slackchlog [OPTIONS]
Options are:
--text-diff-remote Display textual diff between remote and local ChangeLog.
This is the default action.
--text-diff-local Display textual diff for local ChangeLog, that is,
the result of the most recent --text-diff-remote action.
--rss-remote Display remote ChangeLog in RSS format.
--arch=ARCH Slackware architecture (x86, x86_64, arm). Default: detect.
--release=RELEASE Slackware release (current, 14.1, etc.). Default: current.
--timeout=TIMEOUT Timeout (in seconds) for fetching the remote ChangeLog.
Default: 10 seconds.
--cache-dir=DIR Specify an alternative directory for storing ChangeLog's data.
Default: $HOME/.cache/slackware.ChangeLog.
--mirror-file=FILE Specify an alternative mirror list for remote ChangeLog.
Default: $HOME/.config/slackchlog.mirror.txt.
In the case where the default file does not exist and
alternative file is not specified, upstream URLs are used.
--verbose Be verbose (quiet by default).
--help Display this help message and exit.
--version Display version and exit.
Note:
It is perfectly acceptable to specify the same option multiple times.
In such case, the last one takes precedence
I think with all this functionality the script can fulfill the needs of:
- console users,
- crontab users,
- GUI users (provided that your feed reader supports external commad).
Please give the thing a try and let me know what you think.
From my point of view, it's feature complete, so I only accept bug fixes
Should you spot something erroneous, please let me know.
I'm planning to push it to SlackBuilds.org after initial reviews.
For now:
- source (md5: 46bcdcf32410e2345faf616afce1b31e)
- package (md5: 7545bde33add02cb70940c04fc850cd1)
Once the SlackBuild gets accepted on SBo, the package will be removed. [ACCEPTED, REMOVED]
Attached screen shot of slackchlog in action
--
Best regards,
Andrzej Telszewski
Last edited by atelszewski; 09-26-2015 at 04:26 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.