Github messages for voidlinux
 help / color / mirror / Atom feed
From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: minijinja-cli-1.0.12
Date: Tue, 23 Jan 2024 10:35:02 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48336@inbox.vuxu.org> (raw)

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

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

https://github.com/jcgruenhage/void-packages minijinja-cli-1.0.12_1
https://github.com/void-linux/void-packages/pull/48336

New package: minijinja-cli-1.0.12
#### Testing the changes
- I tested the changes in this PR: **YES**

#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES** (compiled)

#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc


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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-minijinja-cli-1.0.12_1-48336.patch --]
[-- Type: text/x-diff, Size: 1201 bytes --]

From 13ac076a282345a9af5fb594f2b49e74d665540f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20Christian=20Gr=C3=BCnhage?=
 <jan.christian@gruenhage.xyz>
Date: Tue, 23 Jan 2024 10:33:50 +0100
Subject: [PATCH] New package: minijinja-cli-1.0.12

---
 srcpkgs/minijinja-cli/template | 13 +++++++++++++
 1 file changed, 13 insertions(+)
 create mode 100644 srcpkgs/minijinja-cli/template

diff --git a/srcpkgs/minijinja-cli/template b/srcpkgs/minijinja-cli/template
new file mode 100644
index 0000000000000..56b392f01e094
--- /dev/null
+++ b/srcpkgs/minijinja-cli/template
@@ -0,0 +1,13 @@
+# Template file for 'minijinja-cli'
+pkgname=minijinja-cli
+version=1.0.12
+revision=1
+build_wrksrc=minijinja-cli
+build_style=cargo
+short_desc="CLI tool that uses MiniJinja to render Jinja2 from CLI"
+maintainer="Jan Christian Grünhage <jan.christian@gruenhage.xyz>"
+license="Apache-2.0"
+homepage="https://github.com/mitsuhiko/minijinja/blob/main/minijinja-cli/README.md"
+changelog="https://github.com/mitsuhiko/minijinja/blob/main/CHANGELOG.md"
+distfiles="https://github.com/mitsuhiko/minijinja/archive/refs/tags/${version}.tar.gz"
+checksum=855f646f4afb4d2467f6118bb164c54f26ce7c26af07f740e2b1fb3f012cd0e8

             reply	other threads:[~2024-01-23  9:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23  9:35 jcgruenhage [this message]
2024-01-23 10:19 ` [PR REVIEW] " tranzystorekk
2024-01-23 10:20 ` tranzystorekk
2024-01-23 13:06 ` jcgruenhage
2024-01-23 13:56 ` tranzystorekk
2024-01-25 12:08 ` [PR PATCH] [Updated] " jcgruenhage
2024-01-25 12:14 ` [PR REVIEW] " jcgruenhage
2024-01-25 12:15 ` jcgruenhage
2024-01-25 12:16 ` tranzystorekk
2024-01-25 12:16 ` jcgruenhage
2024-01-26 12:20 ` jcgruenhage
2024-03-14 11:46 ` [PR PATCH] [Closed]: " jcgruenhage
2024-03-14 11:46 ` 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-48336@inbox.vuxu.org \
    --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).