diff options
author | trevor <trevor@FreeBSD.org> | 2000-10-19 18:47:28 +0800 |
---|---|---|
committer | trevor <trevor@FreeBSD.org> | 2000-10-19 18:47:28 +0800 |
commit | 8c6a2ce37638e39137aa725264cf813c6e0020a7 (patch) | |
tree | b92dafb0123dfbeba102a78639707808390c1216 /Tools/scripts/README | |
parent | a873562dfc06619a1451cddfdc076d3a85f6fa83 (diff) | |
download | freebsd-ports-gnome-8c6a2ce37638e39137aa725264cf813c6e0020a7.tar.gz freebsd-ports-gnome-8c6a2ce37638e39137aa725264cf813c6e0020a7.tar.zst freebsd-ports-gnome-8c6a2ce37638e39137aa725264cf813c6e0020a7.zip |
Add update-patches, a script to generate updated versions of the
patches in a port.
Obtained from: OpenBSD
Diffstat (limited to 'Tools/scripts/README')
-rw-r--r-- | Tools/scripts/README | 20 |
1 files changed, 19 insertions, 1 deletions
diff --git a/Tools/scripts/README b/Tools/scripts/README index 48be3afb69a0..c069063b01da 100644 --- a/Tools/scripts/README +++ b/Tools/scripts/README @@ -24,6 +24,8 @@ portsearch - A utility for searching the ports tree. It allows more detailed search criteria than ``make search key=<string>'' and accepts all perl(1) regular expressions. +update-patches - generates updated patches. + ---------------------------------------------------------------------- consistency-check gives output like: @@ -139,6 +141,22 @@ See the file README.portsearch for further information. ---------------------------------------------------------------------- +The update-patches script looks for files in $WRKSRC (if unset, this defaults +to the work/ subdirectory of the current directory) which have a matching .orig +file. It also looks in $PATCHDIR (if unset, this defaults to the files/ +subdirectory of the current directory) for patches that correspond to the first +set. If the changes in an existing patch do not reflect the changes in the +files in $WRKSRC, the script renames the existing patch by adding the suffix +.orig and generates a new patch in its place. If no patch existed, the new one +is created with a name that contains the path and filename of the file being +patched, except that "/" separators and "." characters are replaced by +underscores: for example, a new patch to $WRKSRC/foo/bar.c would be created as +$PATCHDIR/patch-foo_bar_c. If you save a .orig backup of a file, but don't +change the file, update-patches will generate an empty patch. + +---------------------------------------------------------------------- + NOTE: These scripts need work and are *NOT* safe to use unless you know what they do. Use at your own risk. Patches would be great, but - it is prefered they pass through maintainer of each particular script. + it is preferred they pass through the maintainer of each particular + script. |