automatic import of python-ansible-pygmentsopeneuler20.03

3 files changed, 210 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..8f82b69 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/ansible-pygments-0.1.1.tar.gz
diff --git a/python-ansible-pygments.spec b/python-ansible-pygments.spec
new file mode 100644
index 0000000..f110f04
--- /dev/null
+++ b/python-ansible-pygments.spec
@@ -0,0 +1,208 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-ansible-pygments
+Version:	0.1.1
+Release:	1
+Summary:	Tools for building the Ansible Distribution
+License:	BSD-2-Clause
+URL:		https://github.com/ansible-community/ansible-pygments
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/0b/35/53891104863a04f69ff761cccd9b11784e19793cd318ecff8f2e5c594401/ansible-pygments-0.1.1.tar.gz
+BuildArch:	noarch
+
+Requires:	python3-pygments
+
+%description
+# [Pygments] lexer and style Ansible snippets
+
+[![GitHub Actions CI/CD workflow](https://github.com/ansible-community/ansible-pygments/actions/workflows/ci-cd.yml/badge.svg)](https://github.com/ansible-community/ansible-pygments/actions/workflows/ci-cd.yml)
+[![Codecov badge](https://img.shields.io/codecov/c/github/ansible-community/ansible-pygments)](https://codecov.io/gh/ansible-community/ansible-pygments)
+
+This project provides a [Pygments] lexer that is able to handle
+[Ansible] output. It may be used anywhere Pygments is integrated.
+The lexer is registered globally under the name `ansible-output`.
+
+It also provides a [Pygments] style for tools needing to highlight
+code snippets.
+
+The code is licensed under the terms of the [BSD 2-Clause license].
+
+## Using the lexer in [Sphinx]
+
+Make sure this library in installed in the same env as your [Sphinx]
+automation via `pip install ansible-pygments sphinx`. Then, you should
+be able to use a lexer by its name `ansible-output` in the code blocks
+of your RST documents. For example:
+
+```rst
+.. code-block:: ansible-output
+
+    [WARNING]: Unable to find '/nosuchfile' in expected paths (use -vvvvv to see paths)
+
+    ok: [localhost] => {
+        "msg": ""
+    }
+```
+
+## Using the style in [Sphinx]
+
+It is possible to just set `ansible` in `conf.py` and it will "just
+work", provided that this project is installed alongside [Sphinx] as
+shown above.
+
+```python
+pygments_style = 'ansible'
+```
+
+[Ansible]: https://www.ansible.com/?utm_medium=github-or-pypi&utm_source=ansible-pygments--readme
+[Pygments]: https://pygments.org
+[Sphinx]: https://www.sphinx-doc.org
+[BSD 2-Clause license]: https://opensource.org/licenses/BSD-2-Clause
+
+
+%package -n python3-ansible-pygments
+Summary:	Tools for building the Ansible Distribution
+Provides:	python-ansible-pygments
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-ansible-pygments
+# [Pygments] lexer and style Ansible snippets
+
+[![GitHub Actions CI/CD workflow](https://github.com/ansible-community/ansible-pygments/actions/workflows/ci-cd.yml/badge.svg)](https://github.com/ansible-community/ansible-pygments/actions/workflows/ci-cd.yml)
+[![Codecov badge](https://img.shields.io/codecov/c/github/ansible-community/ansible-pygments)](https://codecov.io/gh/ansible-community/ansible-pygments)
+
+This project provides a [Pygments] lexer that is able to handle
+[Ansible] output. It may be used anywhere Pygments is integrated.
+The lexer is registered globally under the name `ansible-output`.
+
+It also provides a [Pygments] style for tools needing to highlight
+code snippets.
+
+The code is licensed under the terms of the [BSD 2-Clause license].
+
+## Using the lexer in [Sphinx]
+
+Make sure this library in installed in the same env as your [Sphinx]
+automation via `pip install ansible-pygments sphinx`. Then, you should
+be able to use a lexer by its name `ansible-output` in the code blocks
+of your RST documents. For example:
+
+```rst
+.. code-block:: ansible-output
+
+    [WARNING]: Unable to find '/nosuchfile' in expected paths (use -vvvvv to see paths)
+
+    ok: [localhost] => {
+        "msg": ""
+    }
+```
+
+## Using the style in [Sphinx]
+
+It is possible to just set `ansible` in `conf.py` and it will "just
+work", provided that this project is installed alongside [Sphinx] as
+shown above.
+
+```python
+pygments_style = 'ansible'
+```
+
+[Ansible]: https://www.ansible.com/?utm_medium=github-or-pypi&utm_source=ansible-pygments--readme
+[Pygments]: https://pygments.org
+[Sphinx]: https://www.sphinx-doc.org
+[BSD 2-Clause license]: https://opensource.org/licenses/BSD-2-Clause
+
+
+%package help
+Summary:	Development documents and examples for ansible-pygments
+Provides:	python3-ansible-pygments-doc
+%description help
+# [Pygments] lexer and style Ansible snippets
+
+[![GitHub Actions CI/CD workflow](https://github.com/ansible-community/ansible-pygments/actions/workflows/ci-cd.yml/badge.svg)](https://github.com/ansible-community/ansible-pygments/actions/workflows/ci-cd.yml)
+[![Codecov badge](https://img.shields.io/codecov/c/github/ansible-community/ansible-pygments)](https://codecov.io/gh/ansible-community/ansible-pygments)
+
+This project provides a [Pygments] lexer that is able to handle
+[Ansible] output. It may be used anywhere Pygments is integrated.
+The lexer is registered globally under the name `ansible-output`.
+
+It also provides a [Pygments] style for tools needing to highlight
+code snippets.
+
+The code is licensed under the terms of the [BSD 2-Clause license].
+
+## Using the lexer in [Sphinx]
+
+Make sure this library in installed in the same env as your [Sphinx]
+automation via `pip install ansible-pygments sphinx`. Then, you should
+be able to use a lexer by its name `ansible-output` in the code blocks
+of your RST documents. For example:
+
+```rst
+.. code-block:: ansible-output
+
+    [WARNING]: Unable to find '/nosuchfile' in expected paths (use -vvvvv to see paths)
+
+    ok: [localhost] => {
+        "msg": ""
+    }
+```
+
+## Using the style in [Sphinx]
+
+It is possible to just set `ansible` in `conf.py` and it will "just
+work", provided that this project is installed alongside [Sphinx] as
+shown above.
+
+```python
+pygments_style = 'ansible'
+```
+
+[Ansible]: https://www.ansible.com/?utm_medium=github-or-pypi&utm_source=ansible-pygments--readme
+[Pygments]: https://pygments.org
+[Sphinx]: https://www.sphinx-doc.org
+[BSD 2-Clause license]: https://opensource.org/licenses/BSD-2-Clause
+
+
+%prep
+%autosetup -n ansible-pygments-0.1.1
+
+%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-ansible-pygments -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 0.1.1-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..92cac23
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+34b94ea16fc530082f9fa45786468923  ansible-pygments-0.1.1.tar.gz