From: bnhrkn <bnhrkn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: font-latinmodern-otf-2.004
Date: Thu, 26 Aug 2021 07:01:12 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32678@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1598 bytes --]
There is a new pull request by bnhrkn against master on the void-packages repository
https://github.com/bnhrkn/void-packages master
https://github.com/void-linux/void-packages/pull/32678
New package: font-latinmodern-otf-2.004
<!-- 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?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [X] 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/32678.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-32678.patch --]
[-- Type: text/x-diff, Size: 1554 bytes --]
From d7990e21eddeb43738223616f27ce84e08b59f1b Mon Sep 17 00:00:00 2001
From: bnhrkn <github@harkin.tk>
Date: Thu, 26 Aug 2021 00:40:23 -0400
Subject: [PATCH] New package: font-latinmodern-otf-2.004
---
srcpkgs/font-latinmodern-otf/template | 26 ++++++++++++++++++++++++++
1 file changed, 26 insertions(+)
create mode 100644 srcpkgs/font-latinmodern-otf/template
diff --git a/srcpkgs/font-latinmodern-otf/template b/srcpkgs/font-latinmodern-otf/template
new file mode 100644
index 000000000000..1a545b49f793
--- /dev/null
+++ b/srcpkgs/font-latinmodern-otf/template
@@ -0,0 +1,26 @@
+# Template file for 'font-latinmodern-otf'
+pkgname=font-latinmodern-otf
+version=2.004
+revision=1
+create_wrksrc=yes
+depends="font-util xbps-triggers"
+short_desc="Fonts derived from the Computer Modern fonts originally used in TeX"
+maintainer="bnhrkn <github@harkin.tk>"
+license="custom:GFL"
+homepage="http://www.gust.org.pl/projects/e-foundry/latin-modern"
+distfiles="http://www.gust.org.pl/projects/e-foundry/latin-modern/download/lm${version}otf.zip
+ http://www.gust.org.pl/projects/e-foundry/latin-modern/licenses/GUST-FONT-LICENSE.txt"
+checksum="5b0236051d3728be6616f1b274e3b910473875b5a3ef9382f0ef00384ddb161b
+ a746108477b2fa685845e7596b7ad8342bc358704b2b7da355f2df0a0cb8ad85"
+
+skip_extraction="http://www.gust.org.pl/projects/e-foundry/latin-modern/licenses/GUST-FONT-LICENSE.txt"
+
+font_dirs="/usr/share/fonts/OTF"
+
+do_install() {
+ vmkdir usr/share/fonts/OTF
+
+ vcopy *.otf usr/share/fonts/OTF
+
+ vlicense GUST-FONT-LICENSE.txt LICENSE
+}
next reply other threads:[~2021-08-26 5:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 5:01 bnhrkn [this message]
2021-08-26 17:27 ` paper42
2021-08-26 21:46 ` bnhrkn
2021-08-26 21:47 ` [PR PATCH] [Closed]: " bnhrkn
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32678@inbox.vuxu.org \
--to=bnhrkn@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).