|
|
1.1 ! root 1: ! 2: From: shane@mit-ajax (K. Shane Hartman) ! 3: I have created a mechanism for automatically updating your Gnu Emacs ! 4: sources from the sources maintained on mit-prep. To take advantage of this ! 5: mechanism you must have a connection to the internet and do the following: ! 6: ! 7: Obtain the modified version of rcp from mit-prep. This version is upward ! 8: compatible with standard rcp. The relevant files are: ! 9: mit-prep:/u2/emacs/rcp.binary (compiled for vax 4.2) ! 10: mit-prep:/u2/emacs/rcp.1c ! 11: mit-prep:/u2/emacs/RCP.README ! 12: You can use ftp to obtain the files or rcp (the old version will work for ! 13: this, just do 'rcp mit-prep.rcp:/u2/emacs/rcp.binary rcp.binary' ... ! 14: ! 15: If you have a source license, /u2/emacs/rcp.diff may be useful: it is ! 16: a diff of ucb rcp and the modified rcp. ! 17: ! 18: Replace your current copy of rcp with rcp.binary (it must suid to root), ! 19: but keep the old copy around just in case (e.g. rename to rcp.ucb) and ! 20: install the man page. ! 21: ! 22: Now connect to your toplevel emacs directory (which contains src, etc, dbx, ! 23: lisp, and info) and do: ! 24: ! 25: rcp -ruvp "mit-prep.rcp:/u2/emacs/dist/*" . ! 26: ! 27: The new options: v - verbose, u - update, and p - preserve write dates. ! 28: The rcp 'account' supports only the rcp command. ! 29: ! 30: Once you have synchronized with the write dates for the files on prep, the ! 31: above command is sufficient to update all and only those files that have ! 32: changed on prep with respect to your sources. For this scheme to work, you ! 33: must maintain the sources on your own machine and be aware that if you ! 34: change a source on your machine, then rcp can be fooled.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.