diff options
| -rw-r--r-- | .gitignore | 1 | ||||
| -rw-r--r-- | python-patch-ng.spec | 270 | ||||
| -rw-r--r-- | sources | 1 |
3 files changed, 272 insertions, 0 deletions
@@ -0,0 +1 @@ +/patch-ng-1.17.4.tar.gz diff --git a/python-patch-ng.spec b/python-patch-ng.spec new file mode 100644 index 0000000..0ef54c1 --- /dev/null +++ b/python-patch-ng.spec @@ -0,0 +1,270 @@ +%global _empty_manifest_terminate_build 0 +Name: python-patch-ng +Version: 1.17.4 +Release: 1 +Summary: Library to parse and apply unified diffs. +License: MIT +URL: https://github.com/conan-io/python-patch +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/c1/b2/ad3cd464101435fdf642d20e0e5e782b4edaef1affdf2adfc5c75660225b/patch-ng-1.17.4.tar.gz +BuildArch: noarch + + +%description +[](https://travis-ci.org/conan-io/python-patch-ng) +[](https://ci.appveyor.com/project/ConanCIintegration/python-patch-ng) +[](https://pypi.python.org/pypi/patch-ng) + +## Patch NG (New Generation) + +#### Library to parse and apply unified diffs. + +#### Why did we fork this project? + +This project is a fork from the original [python-patch](https://github.com/techtonik/python-patch) project. + +As any other project, bugs are common during the development process, the combination of issues + pull requests are +able to keep the constant improvement of a project. However, both community and author need to be aligned. When users, +developers, the community, needs a fix which are important for their projects, but there is no answer from the author, +or the time for response is not enough, then the most plausible way is forking and continuing a parallel development. + +That's way we forked the original and accepted most of PRs waiting for review since jun/2019 (5 months from now). + +### Features + + * Python 2 and 3 compatible + * Automatic correction of + * Linefeeds according to patched file + * Diffs broken by stripping trailing whitespace + * a/ and b/ prefixes + * Single file, which is a command line tool and a library + * No dependencies outside Python stdlib + * Patch format detection (SVN, HG, GIT) + * Nice diffstat histogram + * Linux / Windows / OS X + * Test coverage + +Things that don't work out of the box: + + * File renaming, creation and removal + * Directory tree operations + * Version control specific properties + * Non-unified diff formats + + +### Usage + +Download **patch_ng.py** and run it with Python. It is a self-contained +module without external dependencies. + + patch_ng.py diff.patch + +You can also run the .zip file. + + python patch-ng-1.17.zip diff.patch + +### Installation + +**patch_ng.py** is self sufficient. You can copy it into your repository +and use it from here. This setup will always be repeatable. But if +you need to add `patch` module as a dependency, make sure to use strict +specifiers to avoid hitting an API break when version 2 is released: + + pip install "patch-ng" + + +### Other stuff + +* [CHANGES](doc/CHANGES.md) +* [LICENSE: MIT](LICENSE) +* [CREDITS](doc/CREDITS) + +%package -n python3-patch-ng +Summary: Library to parse and apply unified diffs. +Provides: python-patch-ng +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-patch-ng +[](https://travis-ci.org/conan-io/python-patch-ng) +[](https://ci.appveyor.com/project/ConanCIintegration/python-patch-ng) +[](https://pypi.python.org/pypi/patch-ng) + +## Patch NG (New Generation) + +#### Library to parse and apply unified diffs. + +#### Why did we fork this project? + +This project is a fork from the original [python-patch](https://github.com/techtonik/python-patch) project. + +As any other project, bugs are common during the development process, the combination of issues + pull requests are +able to keep the constant improvement of a project. However, both community and author need to be aligned. When users, +developers, the community, needs a fix which are important for their projects, but there is no answer from the author, +or the time for response is not enough, then the most plausible way is forking and continuing a parallel development. + +That's way we forked the original and accepted most of PRs waiting for review since jun/2019 (5 months from now). + +### Features + + * Python 2 and 3 compatible + * Automatic correction of + * Linefeeds according to patched file + * Diffs broken by stripping trailing whitespace + * a/ and b/ prefixes + * Single file, which is a command line tool and a library + * No dependencies outside Python stdlib + * Patch format detection (SVN, HG, GIT) + * Nice diffstat histogram + * Linux / Windows / OS X + * Test coverage + +Things that don't work out of the box: + + * File renaming, creation and removal + * Directory tree operations + * Version control specific properties + * Non-unified diff formats + + +### Usage + +Download **patch_ng.py** and run it with Python. It is a self-contained +module without external dependencies. + + patch_ng.py diff.patch + +You can also run the .zip file. + + python patch-ng-1.17.zip diff.patch + +### Installation + +**patch_ng.py** is self sufficient. You can copy it into your repository +and use it from here. This setup will always be repeatable. But if +you need to add `patch` module as a dependency, make sure to use strict +specifiers to avoid hitting an API break when version 2 is released: + + pip install "patch-ng" + + +### Other stuff + +* [CHANGES](doc/CHANGES.md) +* [LICENSE: MIT](LICENSE) +* [CREDITS](doc/CREDITS) + +%package help +Summary: Development documents and examples for patch-ng +Provides: python3-patch-ng-doc +%description help +[](https://travis-ci.org/conan-io/python-patch-ng) +[](https://ci.appveyor.com/project/ConanCIintegration/python-patch-ng) +[](https://pypi.python.org/pypi/patch-ng) + +## Patch NG (New Generation) + +#### Library to parse and apply unified diffs. + +#### Why did we fork this project? + +This project is a fork from the original [python-patch](https://github.com/techtonik/python-patch) project. + +As any other project, bugs are common during the development process, the combination of issues + pull requests are +able to keep the constant improvement of a project. However, both community and author need to be aligned. When users, +developers, the community, needs a fix which are important for their projects, but there is no answer from the author, +or the time for response is not enough, then the most plausible way is forking and continuing a parallel development. + +That's way we forked the original and accepted most of PRs waiting for review since jun/2019 (5 months from now). + +### Features + + * Python 2 and 3 compatible + * Automatic correction of + * Linefeeds according to patched file + * Diffs broken by stripping trailing whitespace + * a/ and b/ prefixes + * Single file, which is a command line tool and a library + * No dependencies outside Python stdlib + * Patch format detection (SVN, HG, GIT) + * Nice diffstat histogram + * Linux / Windows / OS X + * Test coverage + +Things that don't work out of the box: + + * File renaming, creation and removal + * Directory tree operations + * Version control specific properties + * Non-unified diff formats + + +### Usage + +Download **patch_ng.py** and run it with Python. It is a self-contained +module without external dependencies. + + patch_ng.py diff.patch + +You can also run the .zip file. + + python patch-ng-1.17.zip diff.patch + +### Installation + +**patch_ng.py** is self sufficient. You can copy it into your repository +and use it from here. This setup will always be repeatable. But if +you need to add `patch` module as a dependency, make sure to use strict +specifiers to avoid hitting an API break when version 2 is released: + + pip install "patch-ng" + + +### Other stuff + +* [CHANGES](doc/CHANGES.md) +* [LICENSE: MIT](LICENSE) +* [CREDITS](doc/CREDITS) + +%prep +%autosetup -n patch-ng-1.17.4 + +%build +%py3_build + +%install +%py3_install +install -d -m755 %{buildroot}/%{_pkgdocdir} +if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi +if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi +if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi +if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi +pushd %{buildroot} +if [ -d usr/lib ]; then + find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/lib64 ]; then + find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/bin ]; then + find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/sbin ]; then + find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst +fi +touch doclist.lst +if [ -d usr/share/man ]; then + find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst +fi +popd +mv %{buildroot}/filelist.lst . +mv %{buildroot}/doclist.lst . + +%files -n python3-patch-ng -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Thu Mar 09 2023 Python_Bot <Python_Bot@openeuler.org> - 1.17.4-1 +- Package Spec generated @@ -0,0 +1 @@ +6e9371b9e6531ccdfb43e7ad883b3ff5 patch-ng-1.17.4.tar.gz |