Jump to content
CCleaner Community Forums

Software updates


Recommended Posts

Hello

 

In order to enable software updates without reinstalling the whole tool, would it be possible to separate the executable part from a definition part of the program, the latter being updatable via a "Check button" (like SpywareBlaster) ? Thanks in advance.

Link to post
Share on other sites
  • Moderators
Hello

 

In order to enable software updates without reinstalling the whole tool, would it be possible to separate the executable part from a definition part of the program, the latter being updatable via a "Check button" (like SpywareBlaster) ? Thanks in advance.

 

 

 

That ideal may sound good to many however there's a problem with it. That being CCleaner.exe which itself once unpacked/installed is itself larger than the whole size of the setup program. I don't know if MrG changes CCleaner.exe everytime there's a program update or not, however if he does it would negate having such an incremental update approach.

 

Imagine updating every component instead of having just the one setup file, the download size would probably increase as per example for the current v1.23.160:

Single setup file: 498 KB (510,718 bytes)

Updating each file singly: 1.25 MB (1,312,205 bytes)

Link to post
Share on other sites

Hardly seems worth worrying about, it's such a small download as it is.

 

SpywareBlaster, your example, is 2.44 MB. It's a different kettle of fish anyway, a spyware program has to frequently update its definitions in order to stay ahead of the spyware writers. When they make changes to the basic program, though, you have to download a whole new version, just like you do with CCleaner.

Link to post
Share on other sites
  • 2 weeks later...
That ideal may sound good to many however there's a problem with it. That being CCleaner.exe which itself once unpacked/installed is itself larger than the whole size of the setup program. I don't know if MrG changes CCleaner.exe everytime there's a program update or not, however if he does it would negate having such an incremental update approach.

 

Imagine updating every component instead of having just the one setup file, the download size  would probably increase as per example for the current v1.23.160:

  Single setup file: 498 KB (510,718 bytes)

  Updating each file singly: 1.25 MB (1,312,205 bytes)

 

 

 

 

Thanks for your comment, but my problem is that we have a software distribution that implies the packetisation (costs) of every piece of new soft instead of simply take advantage from a "Check new version" called from within the installed application!

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...