From: make-file <make-file@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: font-vazir-code-1.1.2
Date: Tue, 12 Jan 2021 16:48:30 +0100 [thread overview]
Message-ID: <20210112154830.6RmOf6L0zEEigkYNhUbE-FPVpZRC_WuWySWub_TeWRU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27400@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 463 bytes --]
There is an updated pull request by make-file against master on the void-packages repository
https://github.com/make-file/void-packages font-vazir-code
https://github.com/void-linux/void-packages/pull/27400
New package: font-vazir-code-1.1.2
This font support of persian/farsi glyphes in monospaced fonts, which is not found in other already added persian/farsi fonts.
A patch file from https://github.com/void-linux/void-packages/pull/27400.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-font-vazir-code-27400.patch --]
[-- Type: text/x-diff, Size: 1238 bytes --]
From e5200f6f1a495e716c3484da9ec6558ed68188ac Mon Sep 17 00:00:00 2001
From: make-file <makefile@riseup.net>
Date: Thu, 24 Dec 2020 15:03:35 +0330
Subject: [PATCH] New package: font-vazir-code-1.1.2
---
srcpkgs/font-vazir-code/template | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
create mode 100644 srcpkgs/font-vazir-code/template
diff --git a/srcpkgs/font-vazir-code/template b/srcpkgs/font-vazir-code/template
new file mode 100644
index 00000000000..e84f98a3966
--- /dev/null
+++ b/srcpkgs/font-vazir-code/template
@@ -0,0 +1,22 @@
+# Template file for 'font-vazir-code'
+pkgname=font-vazir-code
+version=1.1.2
+revision=1
+create_wrksrc=yes
+depends="font-util"
+short_desc="Persian (farsi) monospaced font"
+maintainer="mkf <makefile@riseup.net>"
+license="custom:Public Domain"
+homepage="https://github.com/rastikerdar/vazir-code-font"
+distfiles="https://github.com/rastikerdar/vazir-code-font/releases/download/v${version}/vazir-code-font-v${version}.zip"
+checksum=5c10819faef1d281db03703a82d498815b3d73b83badfa3100f9bbcd893b071e
+
+font_dirs="/usr/share/fonts/TTF"
+
+do_install() {
+ vmkdir usr/share/fonts/TTF
+ for f in ./*.ttf; do
+ vinstall "$f" 644 usr/share/fonts/TTF
+ done
+ vlicense LICENSE
+}
next prev parent reply other threads:[~2021-01-12 15:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 11:45 [PR PATCH] " make-file
2021-01-12 5:37 ` [PR REVIEW] " ericonr
2021-01-12 15:48 ` make-file [this message]
2021-01-12 15:49 ` make-file
2021-01-15 18:48 ` ericonr
2021-01-16 7:50 ` [PR PATCH] [Updated] " make-file
2021-01-16 15:50 ` [PR REVIEW] " make-file
2021-01-16 15:51 ` make-file
2021-04-18 4:17 ` [PR PATCH] [Closed]: " 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=20210112154830.6RmOf6L0zEEigkYNhUbE-FPVpZRC_WuWySWub_TeWRU@z \
--to=make-file@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).