Best regards dear Subversion team. I want to propose an idea according to
the Tigris.org philosophy about of tools for collaborative software
When somebody creates a program, generates an installer and makes it
available in his/her web page. People download and install it. That is OK.
When an update is done, another installer is added to the web page. People
should realize by themselves about of the update to get the new version and
install it. The developer wants to improve it and programs a routine to
reach the website and find if there is an update and informs to the user.
The user should download it and do all the process again.
The programmer improves the routine and now it downloads the update
automatically and calls the installer process, or creates a repository and
the operating system updates the program automatically (Linux for example).
That is better for the user but requires a lot of effort from each
development team in the world.
In any case, to update the program requires download whole the program or
some files. But the changes are usually in a small segment of code. It could
be inferred, there are a waste of bandwidth. I think, it would be fabulous
if the Subversion team reuses their code to generate a small updater for
general use. It could operate as the following example.
The programmer generates the first installer (version 1.0) and uploads it to
his/her web site; creates a subversion repository in the web site and adds
the programs and their files to that repository. Users download the
installer and sets it up as usual. It contains the svn-updater tool inside.
Anytime the program is launched, it calls the svn-updater tool silently.
A week later the programmer generates a new version. He/she makes another
installer and commits the new versions of the program to the repository.
Suppose the programmer makes it twice more. So the program is in version 1.3
An user with version 1.0 of the program, runs it. The svn-updater connects
to the repository (it ships a configuration file) and detects the new
revisions. It updates the program to the version 1.3 downloading a reduced
amount of bytes as usual.
I know svn already can do it, but svn could be adapted for the program
update facility only. The svn-updater should call the program after
svn-updater runs. What do you think about it?
If already there is a similar tool or my English is abstruse, please forgive
Thanks so much
Received on 2009-05-09 23:54:50 CEST