This project has moved. For the latest updates, please go here.

How is it ensured that RuckZuck always has the latest version?

Topics: Package related
Sep 25, 2015 at 9:59 AM
As far as I understood, the content of RuckZucks's repository is maintained manually. That means, if a new software version is released, a user has to submit that new version to RuckZuck.

If this is the case, I propose to include URL patterns in the package description similar to http://ketarin.canneverbe.com/. Users can then approve new versions in the web interface or rzander manually
Coordinator
Sep 26, 2015 at 9:22 AM
Edited Oct 16, 2015 at 7:44 PM
Yes, it's a manual process. But there are already some mechanism in place to detect changes:
  • Every file download is checked with a hash value. If the hash does not match (e.g. because the vendor has updated the source), the tool will automatically send feedback and to http://ruckzuck.tools and the last 5 packages with Issues will show up on the main page.
  • RuckZuck stores all detected Versions of Software from the "Clients" in a Database. So it's possible to create reports to detect newer Versions... But this only works, if the Software Vendors are using valid Product-Names and Versions... :-(
  • All ProductURLs are monitored with WebSite-Watcher to detect changes on the Vendors Page
  • registered users can provide feedback if they detect an old version
  • everyone can upload a new product or an update of an existing one. An approved Version is protected an cannot be changed anymore.
Currently all of the ~370 Packages where successfully installed within the last 14days. Registered Users have an option in the RuckZuck-Tool to show the top10 of the "oldest" products and the products with most issues in the hope that the community helps to keep the repository up to date...