Github messages for voidlinux
 help / color / mirror / Atom feed
From: krkk <krkk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libheif: enable avif and heif encoding
Date: Sat, 10 Apr 2021 12:48:59 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30118@inbox.vuxu.org> (raw)

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

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

https://github.com/krkk/void-packages libheif-encoding
https://github.com/void-linux/void-packages/pull/30118

libheif: enable avif and heif encoding
#### General
- [ ] 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?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] I generally don't use the affected packages but briefly tested this PR

#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [x] I built this PR locally for my native architecture, (x86_64-glibc)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [x] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl

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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libheif-encoding-30118.patch --]
[-- Type: text/x-diff, Size: 1316 bytes --]

From 7579e648dd2ec01aa0a568f43f420d8bcaf50a00 Mon Sep 17 00:00:00 2001
From: Karol Kosek <krkk@krkk.ct8.pl>
Date: Sat, 10 Apr 2021 11:47:47 +0200
Subject: [PATCH] libheif: enable avif and heif encoding

---
 srcpkgs/libheif/template | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/libheif/template b/srcpkgs/libheif/template
index 64518027febf..5a7af30c347d 100644
--- a/srcpkgs/libheif/template
+++ b/srcpkgs/libheif/template
@@ -1,11 +1,12 @@
 # Template file for 'libheif'
 pkgname=libheif
 version=1.11.0
-revision=1
+revision=2
 build_style=gnu-configure
 configure_args="--disable-option-checking"
 hostmakedepends="automake autoconf pkg-config libtool"
-makedepends="libjpeg-turbo-devel libpng-devel libde265-devel"
+makedepends="libjpeg-turbo-devel libpng-devel libde265-devel x265-devel
+ libaom-devel"
 short_desc="ISO/IEC 23008-12:2017 HEIF file format decoder and encoder"
 maintainer="Kyle Nusbaum <knusbaum+void@sdf.org>"
 license="LGPL-3.0-or-later"
@@ -19,7 +20,7 @@ pre_configure() {
 
 libheif-devel_package() {
 	short_desc+=" - development files"
-	depends="${sourcepkg}>=${version}_${revision} libde265-devel"
+	depends="${sourcepkg}>=${version}_${revision} libde265-devel x265-devel libaom-devel"
 	pkg_install() {
 		vmove usr/include
 		vmove "usr/lib/*.a"

             reply	other threads:[~2021-04-10 10:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-10 10:48 krkk [this message]
2021-04-11  3:09 ` [PR PATCH] [Merged]: " ericonr

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