From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-pytest: install manpage
Date: Thu, 22 Jul 2021 00:01:31 +0200 [thread overview]
Message-ID: <20210721220131.AxS4LX2jrkcLTVyp3hhYq7PdpuQVKHOdeLTrTbxVfF8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32033@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1601 bytes --]
There is an updated pull request by paper42 against master on the void-packages repository
https://github.com/paper42/void-packages pytest-man
https://github.com/void-linux/void-packages/pull/32033
python3-pytest: install manpage
<!-- Mark items with [x] where applicable -->
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/32033.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pytest-man-32033.patch --]
[-- Type: text/x-diff, Size: 2432 bytes --]
From b9127c0f6fc9167fafac2fb51580fd51be92a3e5 Mon Sep 17 00:00:00 2001
From: Michal Vasilek <michal@vasilek.cz>
Date: Sun, 18 Jul 2021 12:05:35 +0200
Subject: [PATCH] python3-pytest: install manpage
---
.../patches/man-remove-sphinx-deps.patch | 19 +++++++++++++++++++
srcpkgs/python3-pytest/template | 9 +++++++--
2 files changed, 26 insertions(+), 2 deletions(-)
create mode 100644 srcpkgs/python3-pytest/patches/man-remove-sphinx-deps.patch
diff --git a/srcpkgs/python3-pytest/patches/man-remove-sphinx-deps.patch b/srcpkgs/python3-pytest/patches/man-remove-sphinx-deps.patch
new file mode 100644
index 000000000000..f3345d6e0a35
--- /dev/null
+++ b/srcpkgs/python3-pytest/patches/man-remove-sphinx-deps.patch
@@ -0,0 +1,19 @@
+we don't need all the dependencies for generating the manpage, avoids needing 4 new packages
+--- a/doc/en/conf.py
++++ b/doc/en/conf.py
+@@ -45,15 +45,11 @@
+ # Add any Sphinx extension module names here, as strings. They can be extensions
+ # coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
+ extensions = [
+- "pallets_sphinx_themes",
+- "pygments_pytest",
+ "sphinx.ext.autodoc",
+ "sphinx.ext.autosummary",
+ "sphinx.ext.intersphinx",
+ "sphinx.ext.todo",
+ "sphinx.ext.viewcode",
+- "sphinx_removed_in",
+- "sphinxcontrib_trio",
+ ]
+
+ # Add any paths that contain templates here, relative to this directory.
diff --git a/srcpkgs/python3-pytest/template b/srcpkgs/python3-pytest/template
index 56ac4b4493af..5ea8912596ea 100644
--- a/srcpkgs/python3-pytest/template
+++ b/srcpkgs/python3-pytest/template
@@ -1,10 +1,10 @@
# Template file for 'python3-pytest'
pkgname=python3-pytest
version=6.2.4
-revision=1
+revision=2
wrksrc="pytest-${version}"
build_style=python3-module
-hostmakedepends="python3-setuptools_scm python3-toml"
+hostmakedepends="python3-setuptools_scm python3-toml python3-Sphinx"
depends="python3-py python3-packaging python3-attrs python3-more-itertools
python3-atomicwrites python3-pluggy python3-wcwidth python3-setuptools
python3-iniconfig python3-toml"
@@ -32,6 +32,11 @@ do_check() {
-k 'not test_color_yes and not test_code_highlight'
}
+post_build() {
+ PYTHONPATH=$(pwd)/build/lib/ make -C doc/en man
+ vman doc/en/_build/man/pytest.1
+}
+
post_install() {
mv ${DESTDIR}/usr/bin/pytest ${DESTDIR}/usr/bin/pytest3
mv ${DESTDIR}/usr/bin/py.test ${DESTDIR}/usr/bin/py.test3
next prev parent reply other threads:[~2021-07-21 22:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-18 10:07 [PR PATCH] " paper42
2021-07-21 22:01 ` paper42 [this message]
2021-07-22 20:57 ` [PR PATCH] [Merged]: " Chocimier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210721220131.AxS4LX2jrkcLTVyp3hhYq7PdpuQVKHOdeLTrTbxVfF8@z \
--to=paper42@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).