From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] font-firacode: update to 1.207
Date: Sat, 27 Jul 2019 20:53:40 +0200 [thread overview]
Message-ID: <20190727185340.6cr5iRYDdVPCqH5Qm1pk_g2W0rp1ZSMjeE_Qj605loA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13369@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 323 bytes --]
There is an updated pull request by mobinmob against master on the void-packages repository
https://github.com/mobinmob/void-packages firacode
https://github.com/void-linux/void-packages/pull/13369
font-firacode: update to 1.207
A patch file from https://github.com/void-linux/void-packages/pull/13369.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-firacode-13369.patch --]
[-- Type: text/x-diff, Size: 1282 bytes --]
From ed1a271d0f244628b13a72de44e36b94968370c9 Mon Sep 17 00:00:00 2001
From: mobinmob <mobinmob@disroot.org>
Date: Sat, 27 Jul 2019 21:26:24 +0300
Subject: [PATCH] font-firacode: update to 1.207
---
srcpkgs/font-firacode/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/font-firacode/template b/srcpkgs/font-firacode/template
index e83f5a4cc9f..534b1e217f7 100644
--- a/srcpkgs/font-firacode/template
+++ b/srcpkgs/font-firacode/template
@@ -1,18 +1,18 @@
# Template file for 'font-firacode'
pkgname=font-firacode
-version=1.206
+version=1.207
revision=1
archs=noarch
create_wrksrc=yes
hostmakedepends="unzip"
-font_dirs="/usr/share/fonts/OTF"
short_desc="FiraCode: monospaced font with programming ligatures"
maintainer="Issam Maghni <me@concati.me>"
license="OFL-1.1"
homepage="https://github.com/tonsky/${pkgname#*-}"
changelog="https://github.com/tonsky/FiraCode/raw/master/CHANGELOG.md"
distfiles="${homepage}/releases/download/${version}/${pkgname#*-}_${version}.zip"
-checksum=433e9e059e53ae1e94c674819b73e49d65bd76e3c6ec70f42d2324062ea3210b
+checksum=ba8d1a9ff3ad1bce7decc48db7a1e95c6116959cc5b9b80dc307b615eec3dfee
+font_dirs="/usr/share/fonts/OTF"
do_install() {
install -Dm644 otf/* -t ${DESTDIR}/${font_dirs}
next prev parent reply other threads:[~2019-07-27 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-27 18:27 [PR PATCH] " voidlinux-github
2019-07-27 18:53 ` voidlinux-github [this message]
2019-07-27 18:53 ` [PR PATCH] [Updated] " voidlinux-github
2019-07-28 8:09 ` [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=20190727185340.6cr5iRYDdVPCqH5Qm1pk_g2W0rp1ZSMjeE_Qj605loA@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).