======================
History
-------
This recipe is a fork of yaco.recipe.patch.
Supported options
-----------------
The recipe supports the following options:
patch
Path to patch
Recipe supports a list of patch one by line.
Eg.
patch = path/sub/patch1.patch # comments are supported too
path/sub/patch2.patch # another one
...
patchlocation
Location to apply patch
binary-patch
Location of patch binary. Use patch in $PATH by default if any is specified.
update_mode
'apply' : patch will be re-applied at each update
'reverse_then_apply': path will be reversed then reapply
'do_nothing' (DEFAULT): ...
Example usage
-------------
We'll start by creating a buildout that uses the recipe::
>>> write('buildout.cfg',
... """
... [buildout]
... parts = testpatch
...
... [testpatch]
... recipe = inouk.recipe.patch
... patch = %(patch)s
... patchlocation = %(patchlocation)s
... """ % { 'patch' : 'patch/example-test.patch', 'example/' : 'value2'}
... update_mode = apply
...)
Running the buildout gives us::
>>> print 'start', system(buildout)
Installing testpatch.
Contributors
============
"Cyril MORISSE", Twitter: @cmorisse
"Assem BAYAHI", http://www.linkedin.com/in/bayahiassem/en
Change history
==============
0.1.2 (2014-06-28)
----------------
- Add readme.txt
- Add support for patches list in patch directive
0.1.1 (2013-06-02)
----------------
- Add support for update and add update_mode parameter
0.1 (2013-05-28)
----------------
- inouk.recipe.patch Initial version. Fork of yaco.recipe.patch
Metadata
Release files for inouk.recipe.patch 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| inouk.recipe.patch-0.1.2.tar.gz | 3.9 kB | Without provenance | Details for inouk.recipe.patch-0.1.2.tar.gz |
Release files / inouk.recipe.patch-0.1.2.tar.gz
| Download URL | inouk.recipe.patch-0.1.2.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
323ee4a9ab9153bbf1cb860189279a56016f29e3126d869d282e72224fdc041b
|
|
BLAKE2b-256 checksum How to use checksums |
05cad7f948f91af4c3235d21812324965cb56d27ade4a178d127cbd34fcc5645
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for inouk.recipe.patch 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.