Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: khmer-fonts-ttf-5.0
Date: Sat, 29 Jun 2019 08:55:07 +0200	[thread overview]
Message-ID: <20190629065507.Pn35h1OlcboSnQYt41sy7SszhiWoB53gD_Km5Txy04g@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12714@inbox.vuxu.org>

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

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

https://github.com/zdtcd/void-packages khmer-fonts
https://github.com/void-linux/void-packages/pull/12714

New package: khmer-fonts-ttf-5.0


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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-khmer-fonts-12714.patch --]
[-- Type: application/text/x-diff, Size: 1325 bytes --]

From b91841233d2f49345b57bdafd4c29b68bedbdd24 Mon Sep 17 00:00:00 2001
From: Doan Tran Cong Danh <congdanhqx@gmail.com>
Date: Thu, 27 Jun 2019 12:13:45 +0700
Subject: [PATCH] New package: khmer-fonts-ttf-5.0

---
 srcpkgs/khmer-fonts-ttf/template | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)
 create mode 100644 srcpkgs/khmer-fonts-ttf/template

diff --git a/srcpkgs/khmer-fonts-ttf/template b/srcpkgs/khmer-fonts-ttf/template
new file mode 100644
index 00000000000..7ebdfbb7ef2
--- /dev/null
+++ b/srcpkgs/khmer-fonts-ttf/template
@@ -0,0 +1,23 @@
+# Template file for 'khmer-fonts-ttf'
+pkgname=khmer-fonts-ttf
+version=5.0
+revision=1
+archs=noarch
+hostmakedepends="unzip"
+depends="font-util"
+short_desc="Fonts for Khmer and Latin script"
+maintainer="Doan Tran Cong Danh <congdanhqx@gmail.com>"
+license="LGPL-2.1-or-later"
+homepage="http://www.khmeros.info/?q=en/fonts"
+distfiles="${SOURCEFORGE_SITE}/khmer/Fonts%20-%20KhmerOS/KhmerOS%20Fonts%20${version}-%20LGPL%20Licence/All_KhmerOS_${version}.zip"
+checksum=62fec2273016fb6e69b18635e696fd2c91953af9cbe757b341721aec2232432e
+
+do_extract() {
+	unzip ${XBPS_SRCDISTDIR}/${pkgname}-${version}/All_KhmerOS_${version}.zip\
+		-d ${wrksrc}
+}
+
+do_install() {
+	vmkdir usr/share/fonts/TTF
+	install -m644 **/*.ttf ${DESTDIR}/usr/share/fonts/TTF
+}

  parent reply	other threads:[~2019-06-29  6:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-27  5:15 [PR PATCH] " voidlinux-github
2019-06-29  6:55 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-29  6:55 ` voidlinux-github [this message]
2019-06-29  8:07 ` voidlinux-github
2019-06-29 17:04 ` voidlinux-github
2019-06-29 17:07 ` voidlinux-github
2019-06-29 18:32 ` voidlinux-github
2019-06-29 18:32 ` voidlinux-github
2019-06-29 18:35 ` voidlinux-github
2019-06-29 18:36 ` voidlinux-github
2019-06-30  1:26 ` voidlinux-github
2019-06-30  1:30 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-30  1:30 ` voidlinux-github
2019-06-30 13:16 ` voidlinux-github
2019-06-30 13:17 ` [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=20190629065507.Pn35h1OlcboSnQYt41sy7SszhiWoB53gD_Km5Txy04g@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).