From: PaperMountainStudio <PaperMountainStudio@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] pylint: install manpages
Date: Sat, 14 Nov 2020 12:54:04 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26371@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 360 bytes --]
There is a new pull request by PaperMountainStudio against master on the void-packages repository
https://github.com/PaperMountainStudio/void-packages 0001-pylint-install-manpages.patch
https://github.com/void-linux/void-packages/pull/26371
pylint: install manpages
A patch file from https://github.com/void-linux/void-packages/pull/26371.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-0001-pylint-install-manpages.patch-26371.patch --]
[-- Type: text/x-diff, Size: 840 bytes --]
From 8f95aa266739e48819a422253d674ff558854a6d Mon Sep 17 00:00:00 2001
From: Paper <paper@tilde.institute>
Date: Sat, 14 Nov 2020 12:50:00 +0100
Subject: [PATCH] pylint: install manpages
---
srcpkgs/pylint/template | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/srcpkgs/pylint/template b/srcpkgs/pylint/template
index 0ad14768d94..379c67948b7 100644
--- a/srcpkgs/pylint/template
+++ b/srcpkgs/pylint/template
@@ -1,7 +1,7 @@
# Template file for 'pylint'
pkgname=pylint
version=2.6.0
-revision=3
+revision=4
wrksrc="pylint-${version}"
build_style=python3-module
hostmakedepends="python3-setuptools"
@@ -28,6 +28,10 @@ post_install() {
vsconf examples/pylintrc_camelcase
vsconf elisp/pylint.el
vsconf elisp/pylint-flymake.el
+
+ for f in man/*; do
+ vman "$f"
+ done
}
python3-pylint_package() {
next reply other threads:[~2020-11-14 11:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-14 11:54 PaperMountainStudio [this message]
2020-11-14 14:45 ` [PR PATCH] [Merged]: " Hoshpak
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26371@inbox.vuxu.org \
--to=papermountainstudio@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).