Re: More on "arch" (our competition)

Some packages are regularly distributed as baselines and patches. For
those packages, exact patching is the expected case. I would guess
this is the problem you are trying to solve.

Scripts such as you've proposed are only reliable on completely
unmodified trees.

Why not, then, use a format that is simpler to parse, contains less
redundant information, and at the same time, if you really want to,
provide a separate, generic, trivial script for "exact" patching?

That separate script could either be included in the email message
(attaching the patch set as a shell "here" document, I suppose) or
simply be added to source distributions of the packages being patched.
A combination of the two approaches would give you one way to
bootstrap the the transition to a new patch set format for packages
regularly distributed as baselines and diffs.

-t

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:57 2006