Hotfix updates

[Dr.Flay]

As TLS components are these days, a) required and b) often compromised or bugged, what about having the ability to pull down the latest DLLs directly ?

And related, how will you go about offering an update if for example, the Lame libs get updated, but nothing in WACUP needs updating ?
Traditionally I would just keep an eye on the rarewares site and manually upgrade, but now you are using your own optimised build, so would rather stick with that.

[dro]

It comes down to requiring timely updates coming from me to provide updates for things as needed (be it something I notice or something that's reported).

At the moment I've had a bum period in getting builds out but releases will go up & down depending on what's being worked on or what else is needed.

In that example you could use a newer version as long as it's interface compatible (which would be likely) & it's more convenience of size / compiler solution that is the difference with most of my supporting dll builds that are starting to constitute a WACUP release.

However I've got to finish off an updater mode but I'm not generally going to be looking at doing per-release patches as it's often simpler with the size of what's being installed (the installer is generally ranging from 5-7MB depending on build type, etc) that it'd just pull down the whole installer & run that based on the user's config options (there's another thread about what was mentioned as being ok to do about updating options that I've got to implement for a v1.0).

-dro