View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000035 | unreal | ircd | public | 2002-01-10 23:22 | 2015-07-19 18:55 |
| Reporter | Assigned To | syzop | |||
| Priority | high | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | no change required | ||
| Product Version | 3.2-beta12 | ||||
| Summary | 0000035: Make http://update.unrealircd.com | ||||
| Description | ./update or update.exe would look up this site, download a list of updates, perhaps add some form goodies ./update in old still downloads from unreal.tspre.org/update.sh, we change this to a shell script that downloads update.c, compiles it, and replaces ./update script with it | ||||
| Steps To Reproduce | Work out update format | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
Well since I did some work with update.exe already, lemme give you the format I've been using. Each update is specified by the text followed by a CRLF or LF. The format for the information is as follows: <platform> <method> <location> <parameters> <released_at> <valid_for> <name> <description> Platform is the OS (valid: win32, unix, amiga) Method is the protocol used to retrieve the file (valid: (for windows) http, ftp (for unix) cvs, http (for amiga) http) Location is <method> specific, if method is http then this is a URL specifying the location of the file, if method is ftp it should be an ftp url, if method is cvs, this should be a standard cvs string ex., :pserver:[email protected]:/home/cmunk/cvsroot Parameters is (as far as I can see) only needed for CVS, this is a comma seperated list of the parameters to send to the CVS server to retrieve the update. If no parameters are required this should be the character string NULL. Released_at is a unix time string that specifies the time which the patch was released. Valid_for is a comma seperated list of the versions for which this update is valid. Name is the name that will be displayed to the user who is preforming the update. Description is a brief description about what the update does such as what bug it fixes, major features added, etc. Thats just my ideas, definately needs more suggestions/revisions to work perfectly, but it's a start. |
|
|
Any plans to implement this in the next few years? :) |
|
|
Doable. But downloading a whole new version and recompiling the whole thing again isn't my idea of an update. The server would keep a list of the changed files in the latest version, and the update script would only download/replace and recompile these files only. This is something I would really like to do, even with a GUI in Qt. |
