From: Barbaross93 <Barbaross93@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] font-spleen: include otb version
Date: Tue, 09 Aug 2022 19:47:28 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38557@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 478 bytes --]
There is a new pull request by Barbaross93 against master on the void-packages repository
https://github.com/Barbaross93/void-packages spleen
https://github.com/void-linux/void-packages/pull/38557
font-spleen: include otb version
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
A patch file from https://github.com/void-linux/void-packages/pull/38557.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-spleen-38557.patch --]
[-- Type: text/x-diff, Size: 1125 bytes --]
From ff409dbdfd05ef62d1c5066e92b96a6530c7aee5 Mon Sep 17 00:00:00 2001
From: Barbaross <cullen.ross@proton.me>
Date: Tue, 9 Aug 2022 13:44:58 -0400
Subject: [PATCH] font-spleen: include otb version
---
srcpkgs/font-spleen/template | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/font-spleen/template b/srcpkgs/font-spleen/template
index 0a7873adaceb..36a48d96c314 100644
--- a/srcpkgs/font-spleen/template
+++ b/srcpkgs/font-spleen/template
@@ -1,12 +1,12 @@
# Template file for 'font-spleen'
pkgname=font-spleen
version=1.9.1
-revision=1
+revision=2
wrksrc="spleen-${version}"
build_style=gnu-makefile
make_cmd=bmake
-make_build_target="pcf psf"
-hostmakedepends="bmake bdftopcf bdf2psf"
+make_build_target="pcf psf otb"
+hostmakedepends="bmake bdftopcf bdf2psf fonttosfnt"
depends="font-util"
short_desc="Monospaced bitmap fonts"
maintainer="Renato Aguiar <renato@renatoaguiar.net>"
@@ -42,5 +42,8 @@ do_install() {
done
vinstall fonts.alias 644 usr/share/fonts/X11/spleen
+ for f in *.otb; do
+ vinstall $f 644 usr/share/fonts/X11/spleen
+ done
vlicense LICENSE
}
next reply other threads:[~2022-08-09 17:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 17:47 Barbaross93 [this message]
2022-08-11 7:15 ` [PR REVIEW] " classabbyamp
2022-08-11 7:15 ` classabbyamp
2022-08-11 8:47 ` paper42
2022-08-11 11:01 ` [PR REVIEW] " Barbaross93
2022-08-11 11:02 ` [PR PATCH] [Updated] " Barbaross93
2022-08-11 11:06 ` Barbaross93
2022-08-13 19:36 ` [PR PATCH] [Merged]: " classabbyamp
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-38557@inbox.vuxu.org \
--to=barbaross93@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).