Github messages for voidlinux
 help / color / mirror / Atom feed
From: PaperMountainStudio <PaperMountainStudio@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] [RFC] asciidoc: use python3
Date: Wed, 29 Jul 2020 10:11:01 +0200	[thread overview]
Message-ID: <20200729081101.aVirU_ySIomnXpZ72pSxJ5asXlH_5_l7jhAgEApkGTY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17774@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 350 bytes --]

There is an updated pull request by PaperMountainStudio against master on the void-packages repository

https://github.com/PaperMountainStudio/void-packages asciidoc-python3
https://github.com/void-linux/void-packages/pull/17774

[RFC] asciidoc: use python3


A patch file from https://github.com/void-linux/void-packages/pull/17774.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-asciidoc-python3-17774.patch --]
[-- Type: text/x-diff, Size: 1568 bytes --]

From 2b46f64162d4d2416fe24966b90dc8bd6388c642 Mon Sep 17 00:00:00 2001
From: Paper <paper@tilde.institute>
Date: Sun, 14 Jun 2020 09:50:49 +0200
Subject: [PATCH] asciidoc: update to 9.0.2, use python3

---
 srcpkgs/asciidoc/template | 19 ++++++++-----------
 1 file changed, 8 insertions(+), 11 deletions(-)

diff --git a/srcpkgs/asciidoc/template b/srcpkgs/asciidoc/template
index b0b7817975b..5665577bacb 100644
--- a/srcpkgs/asciidoc/template
+++ b/srcpkgs/asciidoc/template
@@ -1,23 +1,20 @@
 # Template file for 'asciidoc'
 pkgname=asciidoc
-version=8.6.10
-revision=2
+version=9.0.2
+revision=1
 archs=noarch
+wrksrc=${pkgname}-py3-${version}
 build_style=gnu-configure
-hostmakedepends="automake docbook-xsl libxslt python"
-depends="docbook-xsl libxslt python"
+hostmakedepends="automake docbook-xsl libxslt python3"
+depends="docbook-xsl libxslt python3"
 conf_files="/etc/asciidoc/filters/*/*.conf /etc/asciidoc/*.conf"
 short_desc="Text based document generation"
 maintainer="Orphaned <orphan@voidlinux.org>"
-homepage="http://asciidoc.org/"
 license="GPL-2.0-or-later"
-distfiles="https://github.com/asciidoc/asciidoc/archive/${version}.tar.gz"
-checksum=9e52f8578d891beaef25730a92a6e723596ddbd07bfe0d2a56486fcf63a0b983
+homepage="https://asciidoc.org/"
+distfiles="https://github.com/asciidoc/asciidoc-py3/archive/${version}.tar.gz"
+checksum=ea73425151f56f278433e442f8b5085599765fa120574db65e6d053eb52927e2
 
 pre_configure() {
 	autoreconf -fi
 }
-
-post_install() {
-	vinstall vim/syntax/asciidoc.vim 644 usr/share/vim/vimfiles/syntax asciidoc.vim
-}

  parent reply	other threads:[~2020-07-29  8:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-25 21:30 [PR PATCH] " voidlinux-github
2020-07-08  8:37 ` [PR PATCH] [Updated] " PaperMountainStudio
2020-07-26  5:41 ` sgn
2020-07-29  8:04 ` [PR PATCH] [Updated] " PaperMountainStudio
2020-07-29  8:11 ` PaperMountainStudio [this message]
2020-07-29  9:31 ` PaperMountainStudio
2020-07-29 13:15 ` [PR PATCH] [Merged]: " sgn

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=20200729081101.aVirU_ySIomnXpZ72pSxJ5asXlH_5_l7jhAgEApkGTY@z \
    --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).