Github messages for voidlinux
 help / color / mirror / Atom feed
From: kawaiiamber <kawaiiamber@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: imlib2-heic-0.1.0
Date: Wed, 13 Jan 2021 09:30:49 +0100	[thread overview]
Message-ID: <20210113083049.d1KogBWg1VmRXgoVIfpuQuNLYFw88HNYHITZO0CASZ4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27814@inbox.vuxu.org>

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

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

https://github.com/kawaiiamber/void-packages imlib2-heic
https://github.com/void-linux/void-packages/pull/27814

New package: imlib2-heic-0.1.0
Closes [this](https://github.com/void-linux/void-packages/issues/27597). [WIP] as I'm not too confident if I included the licenses correctly. `./xbps-src pkg imlib2-heic` passes locally on my end, hoping for the best ~

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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-imlib2-heic-27814.patch --]
[-- Type: text/x-diff, Size: 1067 bytes --]

From 31c2fcec04cfeeb30228c946393bc4e9c9a1e24e Mon Sep 17 00:00:00 2001
From: KawaiiAmber <japaneselearning101@gmail.com>
Date: Sat, 12 Dec 2020 12:10:54 -0700
Subject: [PATCH] New package: imlib2-heic-0.1.0

---
 srcpkgs/imlib2-heic/template | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
 create mode 100644 srcpkgs/imlib2-heic/template

diff --git a/srcpkgs/imlib2-heic/template b/srcpkgs/imlib2-heic/template
new file mode 100644
index 00000000000..eed9d3aad40
--- /dev/null
+++ b/srcpkgs/imlib2-heic/template
@@ -0,0 +1,17 @@
+# Template file for 'imlib2-heic'
+pkgname=imlib2-heic
+version=0.1.1
+revision=1
+build_style=gnu-makefile
+hostmakedepends="pkg-config"
+makedepends="imlib2-devel libheif-devel"
+short_desc="HEIC/HEIF decoder for imlib2 (feh)"
+maintainer="KawaiiAmber <japaneselearning101@gmail.com>"
+license="BSD-3-Clause"
+homepage="https://github.com/vi/imlib2-heic"
+distfiles="${homepage}/archive/v${version}.tar.gz"
+checksum=8e7771903ef2e8718e17f228e7fcdb1aeb889e57c9d846b6708d45b6310a3856
+
+post_install() {
+	vlicense LICENSE
+}

  parent reply	other threads:[~2021-01-13  8:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-10 20:46 [PR PATCH] [WIP] " kawaiiamber
2021-01-10 20:46 ` [PR PATCH] [Updated] " kawaiiamber
2021-01-10 21:22 ` kawaiiamber
2021-01-13  0:34 ` kawaiiamber
2021-01-13  0:36 ` kawaiiamber
2021-01-13  0:41 ` [PR PATCH] [Updated] " kawaiiamber
2021-01-13  8:30 ` kawaiiamber [this message]
2021-01-13  8:31 ` kawaiiamber
2021-01-13 10:37 ` DirectorX
2021-01-13 11:05 ` [PR PATCH] [Updated] New package: imlib2-heic-0.1.1 kawaiiamber
2021-04-18  4:22 ` [PR REVIEW] " ericonr
2021-04-21 23:43 ` kawaiiamber
2021-04-22  0:19 ` ericonr
2021-04-22  0:19 ` ericonr
2021-04-22  0:20 ` ericonr
2021-04-22  1:13 ` [PR PATCH] [Updated] " kawaiiamber
2021-04-22  1:13 ` [PR REVIEW] " kawaiiamber
2022-02-14 18:21 ` [PR PATCH] [Closed]: " q66

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=20210113083049.d1KogBWg1VmRXgoVIfpuQuNLYFw88HNYHITZO0CASZ4@z \
    --to=kawaiiamber@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).