[bug-patch] Re: GNU patch: new 2.6 release

[Andreas Gruenbacher]

On Friday 13 November 2009 11:12:41 pm Claudio Fontana wrote:
> src/patch.o: In function `make_temp':
> /home/claudio/.sourceinstall/build/patch-2.6/src/patch.c:1531:
> warning: the use of `mktemp' is dangerous, better use `mkstemp'

That's a known issue (http://savannah.gnu.org/bugs/?26099) which has been 
reported repeatedly in the past, but not actually a bug. I'm still planning to 
get rid of the warning though.

> I will test patch more in the next days.. in any case, I saw you put
> there some additional workarounds for Perforce,
> have you considered ClearCase yet?

You mean this entry in NEWS?

* Change the default value of PATCH_GET to 0.  (Previously, the default was 0
  under POSIXLY_CORRECT and negative otherwise; this is causing problems
  particularly with Perforce.)

The man page says:

    -g num  or  --get=num
        This option controls patch's actions when a file is under RCS or
        SCCS control, and does not exist or is read-only and matches the default
        version, or when a file is under ClearCase or Perforce control and
        does not exist.  If num is positive, patch gets (or checks out) the 
file from
        the revision control system; if zero, patch ignores RCS, ClearCase,
        Perforce, and SCCS and does not get the file; and if negative, patch 
asks
        the user whether to get the file.  The default value of this option is 
given
        by the value of the PATCH_GET environment variable if it is set; if not,
        the default value is zero.

> In addition to that, I always had a problem when trying to apply -p0
> patches that contain versioned filenames (containing "@@").

Could you please give an example and describe what the expected and observed 
behaviors are exactly?

Thanks,
Andreas