Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!columbia!rutgers!sri-spam!wohler From: wohler@sri-spam.istc.sri.com (Bill Wohler) Newsgroups: comp.emacs Subject: Re: How are diff files used to update the distribution ? Message-ID: <9831@sri-spam.istc.sri.com> Date: Thu, 22-Jan-87 01:05:33 EST Article-I.D.: sri-spam.9831 Posted: Thu Jan 22 01:05:33 1987 Date-Received: Thu, 22-Jan-87 06:13:13 EST References: <8701192041.AA01426@EDDIE.MIT.EDU> <5623@cbrma.att.com> Reply-To: wohler@sri-spam.UUCP (Bill Wohler) Organization: SRI International, Menlo Park Lines: 33 Summary: the actual process the following is an excerpt from a README.local file that i maintain in my emacs directory in case i die tomorrow and someone should have to maintain emacs here. it describes the method that use to get patch to work as automatically as possible with the minimum amount of editing of the diff file. i'll welcome any improvements in wording or design to this method. --bw NOTE: the example given in this README file was that we were upgrading from dist-18.33 to dist-18.35. * Incorporate the diff file. ** Edit the diff file. *** Write the "new file" portions to their respective files. *** Remove any diff references to non-existent files. For instance, I do not maintain cpp or shortnames directories. ** Run patch on the diff file. *** First, move the diff file into the same directory that contains the emacs directory. Make a symbolic link from a file called dist-18.33 to the emacs directory. The actual name of this file is taken from the diff file. Pick either the old or new distribution name for the symbolic link. *** Then run "patch -p < diff-18.33-18.35" (or whatever your patch file is) and watch the fun. The symbolic link can then be removed. You may have to manually edit some files if the patch fails--this is where you get to be creative. ** Remove the .rej and .orig files created by patch once you feel that everything is right.