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.
shilo u used your script but pointed it to the /source folder and it still doesn't update the slack-desc and the .Slackbuild. Is that because they have the same name?
the first time i run it it gets all the files, including the .Slackbuild and the slack-desc. But when Pat updates lets say groff to 1.19.1 (only because it was the first on the changelog) the slack-desc and the .Slackbuild still are for the old version, even thou on the server it is current on the server. So I end up getting them manually.
Tinkster was asking if your machine's 'date' setting is perhaps ahead of the server's. If so, the files on your hard drive will always appear newer, hence rsync will not grab them.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.