From: tranzystorek-io <tranzystorek-io@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] comrak: update to 0.18.0
Date: Fri, 31 Mar 2023 13:46:32 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43141@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]
There is a new pull request by tranzystorek-io against master on the void-packages repository
https://github.com/tranzystorek-io/void-packages comrak
https://github.com/void-linux/void-packages/pull/43141
comrak: update to 0.18.0
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- 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/43141.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-comrak-43141.patch --]
[-- Type: text/x-diff, Size: 1288 bytes --]
From b84cac70af8576e4e5e2b3c7a8429eb07bee3c4f Mon Sep 17 00:00:00 2001
From: Marcin Puc <tranzystorek.io@protonmail.com>
Date: Fri, 31 Mar 2023 13:45:46 +0200
Subject: [PATCH] comrak: update to 0.18.0
---
srcpkgs/comrak/template | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/comrak/template b/srcpkgs/comrak/template
index de5c8679d4bd..7851c9c1a14c 100644
--- a/srcpkgs/comrak/template
+++ b/srcpkgs/comrak/template
@@ -1,15 +1,19 @@
# Template file for 'comrak'
pkgname=comrak
-version=0.16.0
+version=0.18.0
revision=1
build_style=cargo
+hostmakedepends="pkg-config"
+makedepends="oniguruma-devel"
short_desc="CommonMark + GFM compatible Markdown parser and renderer"
maintainer="jcgruenhage <jan.christian@gruenhage.xyz>"
license="BSD-2-Clause"
homepage="https://github.com/kivikakk/comrak"
changelog="https://github.com/kivikakk/comrak/raw/main/changelog.txt"
distfiles="https://github.com/kivikakk/comrak/archive/${version}.tar.gz"
-checksum=72f7ecbef6df715f14a61242fea0cbb450bbf1d10eb38acd99502daed04f8c07
+checksum=fce21e382e3c21064a364c6993ff6387fd481efd859c71c7e059cbfcdf14e832
+
+export RUSTONIG_SYSTEM_LIBONIG=1
case "$XBPS_TARGET_MACHINE" in
# Tests don't compile on i686: ran out of registers during register allocation
next reply other threads:[~2023-03-31 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 11:46 tranzystorek-io [this message]
2023-04-01 20:45 ` tranzystorek-io
2023-04-01 20:45 ` [PR PATCH] [Closed]: " tranzystorek-io
2023-04-01 20:19 [PR PATCH] " jcgruenhage
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-43141@inbox.vuxu.org \
--to=tranzystorek-io@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).