Github messages for voidlinux
 help / color / mirror / Atom feed
From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-ruamel.yaml.clib: regenerate Cython binding
Date: Thu, 22 Sep 2022 19:27:35 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39421@inbox.vuxu.org> (raw)

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

There is a new pull request by sgn against master on the void-packages repository

https://github.com/sgn/void-packages ruamel.yaml.clib-py-3-11
https://github.com/void-linux/void-packages/pull/39421

python3-ruamel.yaml.clib: regenerate Cython binding
Maybe merge into #39346 

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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-ruamel.yaml.clib-py-3-11-39421.patch --]
[-- Type: text/x-diff, Size: 1797 bytes --]

From 1a07ec1c2dd49ad6f4a3835dbbba9827effc59b4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C4=90o=C3=A0n=20Tr=E1=BA=A7n=20C=C3=B4ng=20Danh?=
 <congdanhqx@gmail.com>
Date: Fri, 23 Sep 2022 00:25:44 +0700
Subject: [PATCH] python3-ruamel.yaml.clib: regenerate Cython binding

---
 srcpkgs/python3-ruamel.yaml.clib/template | 19 +++++++++++++------
 1 file changed, 13 insertions(+), 6 deletions(-)

diff --git a/srcpkgs/python3-ruamel.yaml.clib/template b/srcpkgs/python3-ruamel.yaml.clib/template
index 97f2fe6b76e9..939cc6d30a09 100644
--- a/srcpkgs/python3-ruamel.yaml.clib/template
+++ b/srcpkgs/python3-ruamel.yaml.clib/template
@@ -2,22 +2,29 @@
 pkgname=python3-ruamel.yaml.clib
 version=0.2.6
 revision=3
-wrksrc="ruamel.yaml.clib-${version}"
+wrksrc="yaml.clib-${version}"
 build_style=python3-module
-hostmakedepends="python3-setuptools"
+hostmakedepends="python3-setuptools python3-Cython"
 makedepends="python3-devel"
 depends="python3"
 short_desc="Reader, parser and emitter for ruamel.yaml (Python3)"
 maintainer="Andrew Benson <abenson+void@gmail.com>"
 license="MIT"
 homepage="http://yaml.readthedocs.io/"
-distfiles="${PYPI_SITE}/r/ruamel.yaml.clib/ruamel.yaml.clib-${version}.tar.gz"
-checksum=4ff604ce439abb20794f05613c374759ce10e3595d1867764dd1ae675b85acbd
+# distfiles="${PYPI_SITE}/r/ruamel.yaml.clib/ruamel.yaml.clib-${version}.tar.gz"
+distfiles="https://github.com/ruamel/yaml.clib/archive/refs/tags/${version}.tar.gz"
+checksum=8cf038c76dd3c5c3a4954bf5232e7eca248050688c0592fa41ca507578790d8a
 
 export RUAMEL_NO_PIP_INSTALL_CHECK=1
+make_check=no
 
-do_check() {
-	: test not found
+pre_configure() {
+	mkdir ruamel.yaml.clib
+	cp _ruamel_yaml.pxd _ruamel_yaml.pyx ruamel.yaml.clib
+	cd ruamel.yaml.clib
+	cython -3 _ruamel_yaml.pyx
+	cp * ..
+	cd ..
 }
 
 post_install() {

             reply	other threads:[~2022-09-22 17:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22 17:27 sgn [this message]
2022-09-22 17:43 ` ahesford
2022-09-22 19:15 ` ahesford
2022-09-22 19:15 ` [PR PATCH] [Closed]: " ahesford

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-39421@inbox.vuxu.org \
    --to=sgn@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).