I'm sorry, but you completely miss my point. Read man rsync about its update in place mode. To get this actvated for a new beta iso image download the name of your local old beta iso must be changed to the name of the new beta iso before downloading it so that rsync is tricked into only downloading and patching in the differences. That is the renaming I am talking about.
troels.rsync6.2.pl (free from my web site) does this automatically provided both names obey the Mandrake rpm naming convention, so that troels can identfy the matching local file from the name of the file about to be downloaded, by ignoring the version and patch fields of both. The beta iso names do not follow the Mandrake RPM naming convention, so troels cannot find any version and patch fields so cannot do this. The version and patch fields could easily be used to distinguish the various betas, rcs, releases, etc. I strongly recommend this change be made. Is everything clear now? Thierry Vignaud wrote: > Ron Stodden <[EMAIL PROTECTED]> writes: > > >>The problem is that the each of the previous beta CD images must >>first be renamed to the name of the new beta to gain the advantages >>you quote (which you deceitfully do not mention), but this cannot be >>done because Mandrake provides no opportunity to do so, since at >>release of a new beta the old one is removed from the mirrors, and >>of course rsync will dutifully delete your copy of it without >>asking. >> >>The proper solution is for Mandrake to use the same naming >>conventions for beta images as for RPMs. > > > we do :-) : new packages as new isos get new names :-) > > >>Why they chose not to is beyond my comprehension (are you listening, >>Warly?). > > > because people're not confused by different betas, rcs, releases > having the same name > -- Ron. [Melbourne, Australia] Web site: http://www.ains.net.au/~ronst/
