[development] RFC: letting modules phone home to check for new releases

Oswald Jaskolla oswald.jaskolla at schieferdecker.com
Tue Nov 21 18:13:24 UTC 2006

Hash: SHA1


I am currently working on a system to automatically install modules (i.e
download and unpack into the appropriate directory) and upgrade modules
(i.e. overwrite present files). The architecture is finished:

- - A module for the GUI and the actual work (not fully implemented yet)
- - A client that provides necessary information to the "GUI and
  functionality" module (one implementation is nearly finished, it lacks
  the ability to provide the actual module files)
- - A server that serves information (module files, version information
  etc.) to client (not implemented, because the client does not need a

My implementation of the client uses a working copy of the HEAD branch
of CVS (that's why I don't need a server at the moment), but there are
numerous other possibilities:
- - CVS (without a working copy)
- - FTP
- - webcvs ... {whatever}

I wouldn't have mentioned this effort in this early stage (it's far from
alpha) but there are three points I have to make:
1. I wouldn't want us to duplicate code or go into different
   (a.k.a incompatible) directions.
2. My module would also benefit from more precise information in the
3. I, too, like to have access to the projects via XML-RPC.

So, what do you think? I tried to understand the other posts of this
discussion, but they seem to revolve around technical aspects that are
not really an issue (at least not at this point of the development
(sure, making it into core would be great)).

- --
Oswald Jaskolla
Ingenieurbüro Richard Schieferdecker
Kreuzherrenstraße 2
D-52062 Aachen

Tel.: 02 41 / 409 54 43
Fax: 02 41 / 477 05 199
mobil: 01 64 / 941 06 75
eMail: oswald.jaskolla at schieferdecker.com
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


More information about the development mailing list