/ 
App-progpatcher-0.002
River stage one • 1 direct dependent • 1 total dependent
/ progpatcher

NAME

progpatcher - Apply a set of patches to your programs

VERSION

This document describes version 0.002 of progpatcher (from Perl distribution App-progpatcher), released on 2017-07-03.

SYNOPSIS

Usage:

% progpatcher [options]

DESCRIPTION

This is like pmpatcher except for programs. You might have a set of patches that you want to apply on programs in the PATH. For example, currently as of this writing I have this on my patches directory:

prog-cpanm.20161127-only_use_uri_from_mirror_where_we_found_module.patch

These patches might be pending for merge upstream, or are of private nature so might never be merged, or of any other nature. Applying patches is a lightweight alternative to creating a fork for each of these programs.

This utility helps you making the process of applying these patches more convenient. Basically this utility just locates all the target modules and feeds all of these patches to the patch program.

To use this utility, first of all you need to gather all your program patches in a single directory (see patches_dir option). Also, you need to make sure that all patches you want to use match this name pattern:

prog-<PROGRAM-NAME>.<TOPIC>.patch

This directory can be the same as the one you use for pmpatcher, since pmpatcher uses another prefix.

Then, to apply all the patches, you just call:

% progpatcher --patches-dir ~/patches

(Or, you might also want to put patches_dir=/path/to/patches into ~/progpatcher.conf to save you from having to type the option repeatedly.)

Example result:

% progpatcher
+--------------------------------------------------------------------------+--------+---------+
| item_id                                                                  | status | message |
+--------------------------------------------------------------------------+--------+---------+
| prog-cpanm.20161127-only_use_uri_from_mirror_where_we_found_module.patch | 200    | Applied |
+--------------------------------------------------------------------------+--------+---------+

If you try to run it again, you might get:

% progpatcher
+--------------------------------------------------------------------------+--------+-----------------+
| item_id                                                                  | status | message         |
+--------------------------------------------------------------------------+--------+-----------------+
| prog-cpanm.20161127-only_use_uri_from_mirror_where_we_found_module.patch | 304    | Already applied |
+--------------------------------------------------------------------------+--------+-----------------+

There's also a --dry-run and a -R (--reverse) option, just like patch.

OPTIONS

* marks required options.

Main options

--patches-dir=s*
--reverse, -R

Configuration options

--config-path=filename

Set path to configuration file.

Can be specified multiple times.

--config-profile=s

Set configuration profile to use.

--no-config

Do not use any configuration file.

Environment options

--no-env

Do not read environment for default options.

Logging options

--debug

Shortcut for --log-level=debug.

--log-level=s

Set log level.

--quiet

Shortcut for --log-level=error.

--trace

Shortcut for --log-level=trace.

--verbose

Shortcut for --log-level=info.

Output options

--format=s

Choose output format, e.g. json, text.

Default value:

undef
--json

Set output format to json.

--naked-res

When outputing as JSON, strip result envelope.

Default value:

0

By default, when outputing as JSON, the full enveloped result is returned, e.g.:

[200,"OK",[1,2,3],{"func.extra"=>4}]

The reason is so you can get the status (1st element), status message (2nd element) as well as result metadata/extra result (4th element) instead of just the result (3rd element). However, sometimes you want just the result, e.g. when you want to pipe the result for more post-processing. In this case you can use `--naked-res` so you just get:

[1,2,3]

Other options

--dry-run

Run in simulation mode (also via DRY_RUN=1).

--help, -h, -?

Display help message and exit.

--version, -v

Display program's version and exit.

COMPLETION

This script has shell tab completion capability with support for several shells.

bash

To activate bash completion for this script, put:

complete -C progpatcher progpatcher

in your bash startup (e.g. ~/.bashrc). Your next shell session will then recognize tab completion for the command. Or, you can also directly execute the line above in your shell to activate immediately.

It is recommended, however, that you install shcompgen which allows you to activate completion scripts for several kinds of scripts on multiple shells. Some CPAN distributions (those that are built with Dist::Zilla::Plugin::GenShellCompletion) will even automatically enable shell completion for their included scripts (using shcompgen) at installation time, so you can immediately have tab completion.

tcsh

To activate tcsh completion for this script, put:

complete progpatcher 'p/*/`progpatcher`/'

in your tcsh startup (e.g. ~/.tcshrc). Your next shell session will then recognize tab completion for the command. Or, you can also directly execute the line above in your shell to activate immediately.

It is also recommended to install shcompgen (see above).

other shells

For fish and zsh, install shcompgen as described above.

CONFIGURATION FILE

This script can read configuration files. Configuration files are in the format of IOD, which is basically INI with some extra features.

By default, these names are searched for configuration filenames (can be changed using --config-path): ~/.config/progpatcher.conf, ~/progpatcher.conf, or /etc/progpatcher.conf.

All found files will be read and merged.

To disable searching for configuration files, pass --no-config.

You can put multiple profiles in a single file by using section names like [profile=SOMENAME] or [SOMESECTION profile=SOMENAME]. Those sections will only be read if you specify the matching --config-profile SOMENAME.

You can also put configuration for multiple programs inside a single file, and use filter program=NAME in section names, e.g. [program=NAME ...] or [SOMESECTION program=NAME]. The section will then only be used when the reading program matches.

Finally, you can filter a section by environment variable using the filter env=CONDITION in section names. For example if you only want a section to be read if a certain environment variable is true: [env=SOMEVAR ...] or [SOMESECTION env=SOMEVAR ...]. If you only want a section to be read when the value of an environment variable has value equals something: [env=HOSTNAME=blink ...] or [SOMESECTION env=HOSTNAME=blink ...]. If you only want a section to be read when the value of an environment variable does not equal something: [env=HOSTNAME!=blink ...] or [SOMESECTION env=HOSTNAME!=blink ...]. If you only want a section to be read when an environment variable contains something: [env=HOSTNAME*=server ...] or [SOMESECTION env=HOSTNAME*=server ...]. Note that currently due to simplistic parsing, there must not be any whitespace in the value being compared because it marks the beginning of a new section filter or section name.

List of available configuration parameters:

format (see --format)
log_level (see --log-level)
naked_res (see --naked-res)
patches_dir (see --patches-dir)
reverse (see --reverse)

ENVIRONMENT

PROGPATCHER_OPT => str

Specify additional command-line options.

FILES

~/.config/progpatcher.conf

~/progpatcher.conf

/etc/progpatcher.conf

HOMEPAGE

Please visit the project's homepage at https://metacpan.org/release/App-progpatcher.

SOURCE

Source repository is at https://github.com/perlancar/perl-App-progpatcher.

BUGS

Please report any bugs or feature requests on the bugtracker website https://rt.cpan.org/Public/Dist/Display.html?Name=App-progpatcher

When submitting a bug or request, please include a test-file or a patch to an existing test-file that illustrates the bug or desired feature.

SEE ALSO

pmpatcher.

AUTHOR

perlancar <perlancar@cpan.org>

COPYRIGHT AND LICENSE

This software is copyright (c) 2017 by perlancar@cpan.org.

This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.