applypatch(1p) [debian man page]

APPLYPATCH(1p)						User Contributed Perl Documentation					    APPLYPATCH(1p)

NAME

       applypatch - apply 'makepatch' generated script to update a source tree

SYNOPSIS

       applypatch [ options ] patch-kit

DESCRIPTION

       Applypatch applies a patch kit as generated by the makepatch program. It performs the following actions:

       o   First, it will extensively verify that the patch kit is complete and did not get corrupted during transfer.

       o   Then it will apply some heuristics to verify that the directory in which the patch will be applied does indeed contain the expected
	   sources.

	   If a corruption or verification error is detected, applypatch exits without making changes.

       o   If the kit is okay, and the directory seems to be the right one: it creates new files and directories as necessary.

       o   Then it runs the patch program to apply the patch to the source files.

       o   Upon completion, obsolete files, directories and .orig files are removed, file modes of new files are set, and the timestamps of all
	   patched files are adjusted.

Applypatch arguments
       Applypatch takes one argument, the name of the patch kit as generated by makepatch. If no name is specified, the patch kit is read from
       standard input.

Applypatch options
       Options are matched case insensitive, and may be abbreviated to uniqueness.

       -directory dir
	   The name of the source directory to be patched.

       -check
	   Perform the checks on the patch kit and patch directory, but do not make any changes.

       -force
	   Force continuation of the patch process even when corruption or verification errors are detected. This is very dangerous!

       -retain
	   Do not remove patch backup files (with extension ".orig") upon completion.

       -patch cmd
	   The patch command to be used. Default is ""patch -p0 -N"".  Additionally, a ""-s"" will be added unless option -verbose was specified.

       -verbose
	   This option will cause applypatch and the patch program to emit verbose progress information.

       -quiet
	   This option will cause applypatch and the patch program to emit no progress information, only error messages.

Environment variables
       SIMPLE_BACKUP_SUFFIX
	   The suffix used by (some versions of?) patch to back up the originals of patched files. Upon completion, these files are removed by
	   applypatch unless the option -retain was specified.	Default value if "".orig"".

SEE ALSO

       makepatch(1), diff(1), patch(1), perl(1), rm(1).

AUTHOR AND CREDITS

       This program is written by Johan Vromans <jvromans@squirrel.nl>.

       See section AUTHOR AND CREDITS of the makepatch program for an extensive list of people that helped one way or another in the makepatch /
       applypatch project.

COPYRIGHT AND DISCLAIMER

       This program is Copyright 1992,1999,2006 by Squirrel Consultancy. All rights reserved.

       This program is free software; you can redistribute it and/or modify it under the terms of either: a) the GNU General Public License as
       published by the Free Software Foundation; either version 1, or (at your option) any later version, or b) the "Artistic License" which
       comes with Perl.

       This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of
       MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See either the GNU General Public License or the Artistic License for more details.

perl v5.10.0							    2006-10-08							    APPLYPATCH(1p)

Check Out this Related Man Page

SVK::Command::Patch(3)					User Contributed Perl Documentation				    SVK::Command::Patch(3)

NAME

       SVK::Command::Patch - Manage patches

SYNOPSIS

	patch --ls    [--list]
	patch --cat   [--view]	     PATCHNAME
	patch --regen [--regenerate] PATCHNAME
	patch --up    [--update]     PATCHNAME
	patch --apply		     PATCHNAME [DEPOTPATH | PATH] [-- MERGEOPTIONS]
	patch --rm    [--delete]     PATCHNAME

OPTIONS

	--depot DEPOTNAME      : operate on a depot other than the default one

DESCRIPTION

       To create a patch, use "commit -P" or "smerge -P".  To import a patch that's sent to you by someone else, just drop it into the "patch"
       directory in your local svk repository. (That's usually "~/.svk/".)

       svk patches are compatible with GNU patch. Extra svk-specific metadata is stored in an encoded chunk at the end of the file.

       A patch name of "-" refers to the standard input and output.

INTRODUCTION

       "svk patch" command can help out on the situation where you want to maintain your patchset to a given project.  It is used under the
       situation that you have no direct write access to remote repository, thus "svk push" cannot be used.

       Suppose you mirror project "foo" to "//mirror/foo", create a local copy on "//local/foo", and check out to "~/dev/foo". After you've done
       some work, you type:

	   svk commit -m "Add my new feature"

       to commit changes from "~/dev/foo" to "//local/foo". If you have commit access to the upstream repository, you can submit your changes
       directly like this:

	   svk push //local/foo

       Sometimes, it's useful to send a patch, rather than submit changes directly, either because you don't have permission to commit to the
       upstream repository or because you don't think your changes are ready to be committed.

       To create a patch containing the differences between "//local/foo" and "//mirror/foo", use this command:

	   svk push -P Foo //local/foo

       The "-P" flag tells svk that you want to create a patch rather than push the changes to the upstream repository.  "-P" takes a single flag:
       a patch name.  It probably makes sense to name it after the feature implemented or bug fixed by the patch. Patch files you generate will be
       created in the "patch" subdirectory of your local svk repository.

       Over time, other developers will make changes to project "foo". From time to time, you may need to update your patch so that it still
       applies cleanly.

       First, make sure your local branch is up to date with any changes made upstream:

	   svk pull //local/foo

       Next, update your patch so that it will apply cleanly to the newest version of the upstream repository:

	   svk patch --update Foo

       Finally, regenerate your patch to include other changes you've made on your local branch since you created or last regenerated the patch:

	   svk patch --regen Foo

       To get a list of all patches your svk knows about, run:

	   svk patch --list

       To see the current version of a specific patch, run:

	   svk patch --view Foo

       When you're done with a patch and don't want it hanging around anymore, run:
	   svk patch --delete Foo

       To apply a patch to the repository that someone else has sent you, run:

	   svk patch --apply - < contributed_feature.patch

perl v5.10.0							    2008-08-04						    SVK::Command::Patch(3)

Linux and UNIX Man Pages

applypatch(1p) [debian man page]

Check Out this Related Man Page