patching utilities?

Is it too late to consider distributing a patching mechanism with the
upcoming release?

Probably everyone has some sort of utility for doing this; I've got
GenPatches and ApplyPatches which traverse the source tree looking for
".orig" files and running diff on any it finds, saving the results to
.patch files. If we packaged these routines (perhaps slightly modified
to encapsulate any patches into a specific area; or we could use someone
else's routines) into a new directory

$(POSTGRESDIR)/patch

then we could generate standard patch tarballs which people could put
into that directory and then automatically expand and apply.

Does anyone want to work on it?

The Developer's FAQ mentions our difforig, cporig, rmorig tools. To
apply the patch, just use any standard patch program, no?

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Is it too late to consider distributing a patching mechanism with
the upcoming release?

The Developer's FAQ mentions our difforig, cporig, rmorig tools. To
apply the patch, just use any standard patch program, no?

OK, I'll look at those...

I'm also suggesting that we have a convention for and place to put the
patch collections, say a directory "patch" just under the main tree.
Then we can distribute tarballs and patch files which just need to be
generated and unpacked in a single location to succeed.

- Tom