Re: lynx-dev lynx2.8.2dev.19 patch #1 ("iso9945" problem)

[pg]

In a recent note, Leonid Pauzner said:

> Date: Fri,  5 Mar 1999 00:25:09 +0300 (MSK)
> 
> Well, I just downloaded dev19 (complete lynx-cur.zip) and found out
> we have now both iso9945_uni.tbl AND iso9945uni.tbl under src/chrtrans/
> That should be stopped :)
> a patch applied:
> 
> * remove iso9945-2 "charset" (which was included/named/mapped by mistake)
> 
I'm grateful.  I'll try this.  But what do I need to do to apply this?
I believe it touches files in several different directories.  Must I
dissect the patch into individual diffs, and cd to each directory and
apply it?

This finally motivates me to submit my makefile target to generate patches.
This generates patches that include the paths, so they can be applied
from a single top directory.  I hope consistency in patch formats will
be a resultant benefit.  Tested on OS/390 and Solaris.

-- gil
=================================================================
%%% Created Sat Feb 20 16:24:41 MST 1999 by target lynx.patch. %%%
diff -brc orig/lynx2-8-2/README lynx2-8-2/README
*** orig/lynx2-8-2/README Wed Feb 17 07:29:33 1999
--- lynx2-8-2/README Sat Feb 20 16:24:01 1999
***************
*** 142,148 ****
     Any messages you wish to post should be sent to address@hidden
     PLEASE use the lynx-dev list, NOT private email to the developers,
     for questions or discussion about Lynx, or contributions of patches.
!    Patches should use the context diff format (diff -c).
  
     You need not be subscribed to the lynx-dev list in order to post.  If
     you post without subscribing, though, you should read replies to your
--- 142,150 ----
     Any messages you wish to post should be sent to address@hidden
     PLEASE use the lynx-dev list, NOT private email to the developers,
     for questions or discussion about Lynx, or contributions of patches.
!    Patches should use the context diff format (diff -c), which can be
!    generated by building the target, "make lynx.patch" after unpacking
!    a pristine copy of the source into a subdirectory called "orig".
  
     You need not be subscribed to the lynx-dev list in order to post.  If
     you post without subscribing, though, you should read replies to your
diff -brc orig/lynx2-8-2/makefile.in lynx2-8-2/makefile.in
*** orig/lynx2-8-2/makefile.in Wed Feb 17 07:29:33 1999
--- lynx2-8-2/makefile.in Sat Feb 20 16:24:01 1999
***************
*** 275,280 ****
--- 275,299 ----
  compress: tar
        cd ..; rm -f $(lynxname).tar.Z; compress -f -v $(lynxname).tar
  
+ # Directory containing reference source for patch generation,
+ #     either absolute or relative to $(top_srcdir)/..
+ REFDIR=orig/$(lynxdir)
+ 
+ lynx.patch: $(top_srcdir) $(top_srcdir)/CHANGES
+       cd  $(top_srcdir)/.. && cd $(REFDIR) && { rm -f \
+               config.log \
+               config.status \
+               lynx_cfg.h \
+                       ; \
+               for I in . src WWW/Library/Implementation; do ( set +e; \
+                       ( set -x; cd $$I && rm -f *.orig *.rej makefile ); : ); 
\
+               done; }
+       ( cd $(top_srcdir)/..; echo "%%% Created `date` by target 
address@hidden %%%"; \
+                       diff -brc $(REFDIR) $(lynxdir) ) \
+               | grep -v '^Common' \
+               | grep -v '^Binary files ' \
+               | grep -v '^Only ' | tee $@ | grep '^--- $(lynxdir)'
+ 
  install: lynx$x install-bin install-man install-cfg @INSTALL_LSS@
        @echo
        @echo "Use $(MAKE) install-help to install the help-files"