Github messages for voidlinux
 help / color / mirror / Atom feed
From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: mdbook-mermaid-0.8.3
Date: Sun, 08 May 2022 18:42:05 +0200	[thread overview]
Message-ID: <20220508164205.u5PKnJ2g1Txbigofextk9d_3E1PrjLaeYD5R3HaoKIQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29850@inbox.vuxu.org>

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

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

https://github.com/jcgruenhage/void-packages mdbook-mermaid-0.8.0_1
https://github.com/void-linux/void-packages/pull/29850

New package: mdbook-mermaid-0.8.3
<!-- Mark items with [x] where applicable -->

#### General
- [x] 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/29850.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-mdbook-mermaid-0.8.0_1-29850.patch --]
[-- Type: text/x-diff, Size: 1078 bytes --]

From f5d63daebde7fc8dfc15769afc483455d9760045 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20Christian=20Gr=C3=BCnhage?=
 <jan.christian@gruenhage.xyz>
Date: Mon, 29 Mar 2021 14:46:19 +0200
Subject: [PATCH] New package: mdbook-mermaid-0.10.0

---
 srcpkgs/mdbook-mermaid/template | 15 +++++++++++++++
 1 file changed, 15 insertions(+)
 create mode 100644 srcpkgs/mdbook-mermaid/template

diff --git a/srcpkgs/mdbook-mermaid/template b/srcpkgs/mdbook-mermaid/template
new file mode 100644
index 000000000000..ec8acd019132
--- /dev/null
+++ b/srcpkgs/mdbook-mermaid/template
@@ -0,0 +1,15 @@
+# Template file for 'mdbook-mermaid'
+pkgname=mdbook-mermaid
+version=0.10.0
+revision=1
+build_style=cargo
+short_desc="Prepocessor for mdbook to add mermaid support"
+maintainer="Jan Christian Grünhage <jan.christian@gruenhage.xyz>"
+license="MPL-2.0"
+homepage="https://github.com/badboy/mdbook-mermaid"
+distfiles="${homepage}/archive/refs/tags/v${version}.tar.gz"
+checksum=7b62ac139c8ece9f21cfdf0b3cd11aabf0d6fdfdfb71848918a028a4cb8de24c
+
+post_install() {
+	vlicense LICENSE
+}

  parent reply	other threads:[~2022-05-08 16:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29 12:49 [PR PATCH] New package: mdbook-mermaid-0.8.0 jcgruenhage
2021-08-11 18:42 ` [PR PATCH] [Updated] " jcgruenhage
2021-08-11 20:19 ` [PR PATCH] [Updated] New package: mdbook-mermaid-0.8.3 jcgruenhage
2022-05-07 21:41 ` Piraty
2022-05-08 16:42 ` jcgruenhage [this message]
2022-05-08 17:20 ` jcgruenhage
2022-05-08 20:40 ` [PR PATCH] [Merged]: New package: mdbook-mermaid-0.10.0 Piraty

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=20220508164205.u5PKnJ2g1Txbigofextk9d_3E1PrjLaeYD5R3HaoKIQ@z \
    --to=jcgruenhage@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).