What I mean is that patch-xemacs.sh is looking for a patch of the name
version+1 whereas what we have is pre-version+1 so it can't find it
Once I have done a mv on the patch file patch works with no problems
Should I try and patch patch-xemacs.sh so it will work for a patch named
pre ?
Or is there in fact a newer version ?
---
Ian
-----Original Message-----
From: SL Baur [mailto:steve@xemacs.org]
Sent: Thursday, April 30, 1998 11:05 PM
To: xemacs-beta(a)xemacs.org
Subject: Re: [Success] 21.0 "Repartida-pre2"
XEmacs Lucid (beta38-pre2) on i 386-pc-cygwin32
Ian MacKinnon <IMacKinnon(a)telia.co.uk> writes:
Does any one else have to hack the filename of the pre
patches
so
patch-xemacs will work ?
Is this the case? The pre-patches are generated the
same way the
beta-n -> beta-n+1 patches are generated and should work
with any
reasonable version of patch.
I know `cvs diff' causes heartache, weeping and gnashing
of teeth with
malformed filenames in patches, but this is the first
I've heard of
`cvs rdiff' having a problem.
Index: xemacs-20.0/CHANGES-beta
diff -u xemacs-20.0/CHANGES-beta:1.125
xemacs-20.0/CHANGES-beta:1.128
--- xemacs-20.0/CHANGES-beta:1.125 Sat Apr 25
21:07:11 1998
+++ xemacs-20.0/CHANGES-beta Wed Apr 29 16:03:42 1998
You have to specify `-p1' to patch to make the first
part of the path
go away, but that should be all.