From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: libicns-0.8.1
Date: Sat, 26 Oct 2019 09:08:42 +0200 [thread overview]
Message-ID: <20191026070842.aZBCiv2Y4JJxndktPmUv1QmOFkVOyGuowxm6yKLCbJc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15789@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 314 bytes --]
There is an updated pull request by teldra against master on the void-packages repository
https://github.com/teldra/void-packages libicns
https://github.com/void-linux/void-packages/pull/15789
New package: libicns-0.8.1
A patch file from https://github.com/void-linux/void-packages/pull/15789.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libicns-15789.patch --]
[-- Type: text/x-diff, Size: 1843 bytes --]
From ab8433ffa42a919ffa27cf21527e17dc382649dc Mon Sep 17 00:00:00 2001
From: teldra <teldra@rotce.de>
Date: Fri, 25 Oct 2019 14:21:59 +0200
Subject: [PATCH] New package: libicns-0.8.1
---
common/shlibs | 1 +
srcpkgs/libicns-devel | 1 +
srcpkgs/libicns/template | 23 +++++++++++++++++++++++
3 files changed, 25 insertions(+)
create mode 120000 srcpkgs/libicns-devel
create mode 100644 srcpkgs/libicns/template
diff --git a/common/shlibs b/common/shlibs
index a280247373a..ee2de95f217 100644
--- a/common/shlibs
+++ b/common/shlibs
@@ -3518,3 +3518,4 @@ libmygpo-qt5.so.1 libmygpo-qt-1.1.0_1
libluv.so.1 libluv-1.30.1.0_1
libarmadillo.so.9 armadillo-9.700.2_1
libvarnishapi.so.2 libvarnishapi-6.3.0_1
+libicns.so.1 libicns-0.8.1_1
diff --git a/srcpkgs/libicns-devel b/srcpkgs/libicns-devel
new file mode 120000
index 00000000000..7902ccb6160
--- /dev/null
+++ b/srcpkgs/libicns-devel
@@ -0,0 +1 @@
+libicns
\ No newline at end of file
diff --git a/srcpkgs/libicns/template b/srcpkgs/libicns/template
new file mode 100644
index 00000000000..1f7fe946cfc
--- /dev/null
+++ b/srcpkgs/libicns/template
@@ -0,0 +1,23 @@
+# Template file for 'libicns'
+pkgname=libicns
+version=0.8.1
+revision=1
+build_style=gnu-configure
+makedepends="libpng-devel jasper-devel"
+short_desc="Library for manipulating icns/IconFamily files"
+maintainer="teldra <teldra@rotce.de>"
+license="LGPL-2.0-only, GPL-2.0-only"
+homepage="https://icns.sourceforge.io/"
+distfiles="https://downloads.sf.net/icns/${pkgname}-${version}.tar.gz"
+checksum=335f10782fc79855cf02beac4926c4bf9f800a742445afbbf7729dab384555c2
+
+libicns-devel_package() {
+ short_desc+=" - development files"
+ depends="${sourcepkg}-${version}_${revision}"
+ pkg_install() {
+ vmove usr/lib/pkgconfig
+ vmove usr/include
+ vmove "usr/lib/*.so"
+ vmove "usr/lib/*.a"
+ }
+}
next prev parent reply other threads:[~2019-10-26 7:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 12:22 [PR PATCH] " voidlinux-github
2019-10-25 12:31 ` [PR PATCH] [Updated] " voidlinux-github
2019-10-25 12:31 ` voidlinux-github
2019-10-26 7:08 ` voidlinux-github
2019-10-26 7:08 ` voidlinux-github [this message]
2019-10-26 12:56 ` [PR PATCH] [Merged]: " voidlinux-github
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=20191026070842.aZBCiv2Y4JJxndktPmUv1QmOFkVOyGuowxm6yKLCbJc@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).