 |
 |
Peter, The ISO in ftp://ftp2.starlink.ac.uk/classic is a good sign, it has the date it was built in the filename. Steve. -----Original Message----- From: Starlink development [mailto:[log in to unmask]] On Behalf Of Peter W. Draper Sent: 19 January 2004 11:49 To: [log in to unmask] Subject: Re: nightly builds On Mon, 19 Jan 2004, David Berry wrote: > > The stardev iso should be generated automatically and put in: > > > > ftp://ftp2.starlink.ac.uk/classic > > > > if the nightly build succeeds. The system still needs automatic generation > > of the versions file. > > Having regularly updated ISOs is good, but I thought one of the advantages > of your previous /stardev system was that using rsync made it easier to > keep your /stardev up to date since 1) it only copied the files which had > changed (although this didn't seem quite to work), and 2) all the copied > files got placed in their correct place without any need to do any > installing. > > I'd prefer to use rsync to keep my /stardev up-to-date rather than > downloading an entire ISO and installing it by hand. Hi Steve, like David (and JAC I suspect) I'd like to be able to reliably rsync too. Since you seem to know when the stardev build continues to successful completion, or not, could you leave some easily recognisable sign about the status of the stardev. The existence or not of some file at the top of the tree should be enough for us to spot that copying is OK (as an ISO was produced from this tree). Cheers, Peter.