From: nmukhachev <nmukhachev@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: source-serif-pro-4.004_1
Date: Tue, 04 May 2021 22:20:13 +0200 [thread overview]
Message-ID: <20210504202013.NSnZoSJPVA_bQFsMTKLblTT2S22K2P65sXQa0y4UfLg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30660@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1609 bytes --]
There is an updated pull request by nmukhachev against master on the void-packages repository
https://github.com/nmukhachev/void-packages master
https://github.com/void-linux/void-packages/pull/30660
New package: source-serif-pro-4.004_1
<!-- Mark items with [x] where applicable -->
#### General
- [x] 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?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/30660.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-30660.patch --]
[-- Type: text/x-diff, Size: 1403 bytes --]
From ece76fde8744c7023eb12f42eb1ce77c36295bc3 Mon Sep 17 00:00:00 2001
From: Nikolay Mukhachev <nikolay-mukhachev@yandex.ru>
Date: Tue, 4 May 2021 00:38:29 +0300
Subject: [PATCH] New package: source-serif-pro-4.004_1
---
srcpkgs/source-serif-pro/template | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
create mode 100644 srcpkgs/source-serif-pro/template
diff --git a/srcpkgs/source-serif-pro/template b/srcpkgs/source-serif-pro/template
new file mode 100644
index 000000000000..06af08b8bcfe
--- /dev/null
+++ b/srcpkgs/source-serif-pro/template
@@ -0,0 +1,24 @@
+# Template file for 'source-serif-pro'
+pkgname=source-serif-pro
+version=4.004
+revision=1
+wrksrc="source-serif-${version}R"
+depends="font-util"
+short_desc="Serif font family for user interface environments"
+maintainer="Nikolay Mukhachev <nikolay-mukhachev@yandex.ru>"
+license="OFL-1.1"
+homepage="https://adobe-fonts.github.io/source-serif/"
+distfiles="https://github.com/adobe-fonts/source-serif/archive/${version}R.tar.gz"
+checksum=dfb364735699cb830caad534cf7741234804d28e4b6fc5e4736b2401f6131aba
+font-dirs="/usr/share/fonts/OTF /usr/share/fonts/TTF"
+
+do_install() {
+ vmkdir usr/share/fonts/TTF
+ vmkdir usr/share/fonts/OTF
+ for f in ${wrksrc}/TTF/*.ttf; do
+ vinstall "$f" 644 usr/share/fonts/TTF
+ done
+ for f in ${wrksrc}/OTF/*.otf; do
+ vinstall "$f" 644 usr/share/fonts/OTF
+ done
+}
next prev parent reply other threads:[~2021-05-04 20:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 21:49 [PR PATCH] " nmukhachev
2021-05-03 23:26 ` [PR REVIEW] " kwshi
2021-05-04 20:20 ` nmukhachev [this message]
2021-05-04 20:22 ` nmukhachev
2021-05-17 19:57 ` Chocimier
2021-05-17 21:08 ` ericonr
2022-05-19 2:16 ` github-actions
2022-06-03 2:11 ` [PR PATCH] [Closed]: " github-actions
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=20210504202013.NSnZoSJPVA_bQFsMTKLblTT2S22K2P65sXQa0y4UfLg@z \
--to=nmukhachev@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).