Versions Selection

[JohnBoyTheGreat]

Not sure how to implement this idea, but software almost always comes in various versions, and it would be nice to be able to select older versions to download, whether to download some, based upon individual selection with check boxes, to download only the latest, or to download all old versions (limited by a specific number to prevent excessive downloads).

In some cases, having a specific version is important, particularly in programming and when trying to repair a broken installation for one of my clients. Sometimes those can be difficult to find. Keeping them on hand is nice, when you need them, and drive space is cheap.

[shawn]

Sadly, this is going to be 100% dependent on the individual application and is beyond the scope of what Ketarin itself is for. Very few download services provide the means to download an older version and those that do each have a different means to implement it.

If all you're concerned with is keeping archival copies locally (and not the URLs to re-download them) then it's as simple as unchecking the box "always delete previously downloaded file" on the "Advanced settings" tab. Make sure your download destination/pattern includes the various important pieces of information you require (application name, bit-type, release type, OS, platform, and so on) to make sure they don't get overwritten.

There are ways to roll your own archive using the global "After updating an application" command, but will be dependent on collecting that information yourself into a persistent database of some sort. I do this in my archival script. In the "after" command I POST to one of my domains with the data from the updated application. The remote script parses the data and inserts it into two separate tables, one that has the archival list of all updates and one that has the most recent version. Among the things I collect are the version, download URL, changelog, OS and release type. Some apps can't be updated directly with Ketarin so we have to use an exit 3 bypass to get around that while keeping the trigger functional.

Afterwards you can do anything you want with the data since you control the database. One example is the XSL I posted here. 

[JohnBoyTheGreat]

On 11/9/2025 at 5:47 PM, shawn said:

Sadly, this is going to be 100% dependent on the individual application and is beyond the scope of what Ketarin itself is for. Very few download services provide the means to download an older version and those that do each have a different means to implement it.

If all you're concerned with is keeping archival copies locally (and not the URLs to re-download them) then it's as simple as unchecking the box "always delete previously downloaded file" on the "Advanced settings" tab. Make sure your download destination/pattern includes the various important pieces of information you require (application name, bit-type, release type, OS, platform, and so on) to make sure they don't get overwritten.

There are ways to roll your own archive using the global "After updating an application" command, but will be dependent on collecting that information yourself into a persistent database of some sort. I do this in my archival script. In the "after" command I POST to one of my domains with the data from the updated application. The remote script parses the data and inserts it into two separate tables, one that has the archival list of all updates and one that has the most recent version. Among the things I collect are the version, download URL, changelog, OS and release type. Some apps can't be updated directly with Ketarin so we have to use an exit 3 bypass to get around that while keeping the trigger functional.

Afterwards you can do anything you want with the data since you control the database. One example is the XSL I posted here. 

I mean, honestly... If I really want all the old versions, I can just go get them, fairly quickly. I just thought it would be nice to have a way to do that automatically when people run into software that they like. I sort of think of Ketarin less as what it was intended to be than what I could use it to do.

For example, I collect software...every version I can find of popular packages. I'm sure there are others who do the same. I can certainly produce Ketarin templates for each one to share with others, but that's clunky. They can easily go download it themselves. But if there was a way to include multiple versions with a dropdown option for a Ketarin template, then anyone could clone the template and choose older versions, then retain the template for the current version. No need to go looking for the downloads for older versions any longer.

It's a niche use, but it's still something I think would be useful for many people.

Also, I absolutely do uncheck the box for deleting the previously downloaded file. Old versions come in handy at times, for numerous reasons.

I personally don't use the update function, because I prefer to manually install all my software, but I think it's a great function for those who use it and I think it's a good idea to include that in any templates I might share. Who knows...maybe I might use it for some apps, someday.

Regarding collecting the information...

I have been collecting the basic information and date downloaded to a text file, but I didn't think to collect all the other information you mentioned. That's a great idea and I'll implement that in the future, I think. I'm trying to make some generic templates that other people can use, which have functions like you have mentioned, and I think that keeping track of downloaded apps in a text file or by some other method is always a good idea.

[shawn]

If you want to keep all the versions that Ketarin downloads just uncheck the box to "Always delete previously downloaded file" and make sure you put the version in the "save to" location. This will do exactly what you want, unless the publisher "forgets" to update the version number or the version parsing function you use breaks. Monitor errors closely and fix any where the version number is empty ASAP.

As long as you use consistent variable names you can use the the after-update command to do anything you want with the data.