Re: Nightly CVS tarballs

|--==> "SJT" == Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp&gt; writes: SY> People who hack from a nightly CVS tarball have to realise SY> that the code they have could be up to 24 hours out of date SY> and need to make allowances for that. Such as, if the current SY> day is broken, wait until the next day's tarball is SY> released. (Of course, they are quite welcome to fix the SY> breakage.) SY> Is that too harsh? SJT> No. But if the point is to make it convenient for people who don't SJT> have normal (== CVS) access to hack bleeding edge XEmacsen, why not SJT> take out some nearly free insurance? OK, I have a working model that I'm testing locally. If all goes well, I'll put it "online" after the weekend. ,----[ main comments from script ] | Commentary: | | This script creates nightly cvs snapshot tarballs of XEmacs 21.5 and | of the XEmacs packages. | | For 21.5 it creates a diff between the latest released beta and | current CVS. It also creates a diff between yesterday's CVS and | today's. Providing that the latter diff is greater than zero bytes | long, a tarball is created and it together with the 2 diffs are | moved to the FTP directory. | | For packages: Check to see if anything has changed since yesterday | and if so, create tarballs and move them to the FTP directory. We | create a "uber" tarball of all packages; a tarball of all standard | packages (if the change was in a standard package); a tarball of all | mule packages (if the change was in a mule package); and a tarball | of any individual package that has changed. | | If any snapshots are created an announcement is sent to xemacs-beta | listing the newly created snapshots. If anything goes wrong an | email is sent to $ADMIN (youngs(a)xemacs.org) so they can fix it. `---- And for those who are interested, here's the script. -- |---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---| | XEmacs - It's not just an editor. | | It's a way of life. | |------------------------------------&lt;youngs(a)xemacs.org&gt;---|