From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] encodings: update to 1.0.6.
Date: Sat, 01 Oct 2022 17:15:19 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39591@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
There is a new pull request by Duncaen against master on the void-packages repository
https://github.com/Duncaen/void-packages encodings-1.0.6
https://github.com/void-linux/void-packages/pull/39591
encodings: update to 1.0.6.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- 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/39591.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-encodings-1.0.6-39591.patch --]
[-- Type: text/x-diff, Size: 1432 bytes --]
From c1c399f69a356ca6c1e91e6450b702e9b24c10e1 Mon Sep 17 00:00:00 2001
From: Duncaen <duncaen@voidlinux.org>
Date: Sat, 1 Oct 2022 17:14:16 +0200
Subject: [PATCH] encodings: update to 1.0.6.
---
srcpkgs/encodings/template | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/srcpkgs/encodings/template b/srcpkgs/encodings/template
index a4baa147efe1..f29dcc1c2f67 100644
--- a/srcpkgs/encodings/template
+++ b/srcpkgs/encodings/template
@@ -1,20 +1,21 @@
# Template file for 'encodings'
pkgname=encodings
-version=1.0.5
-revision=2
+version=1.0.6
+revision=1
build_style=gnu-configure
hostmakedepends="pkg-config font-util"
depends="font-util"
-short_desc="X11 Font Index Generator"
+short_desc="Font encoding tables for libfontenc"
maintainer="Orphaned <orphan@voidlinux.org>"
license="custom:Public domain"
homepage="http://xorg.freedesktop.org"
-distfiles="${XORG_SITE}/font/$pkgname-$version.tar.bz2"
-checksum=bd96e16143a044b19e87f217cf6a3763a70c561d1076aad6f6d862ec41774a31
+distfiles="${XORG_SITE}/font/encodings-${version}.tar.xz"
+checksum=77e301de661f35a622b18f60b555a7e7d8c4d5f43ed41410e830d5ac9084fc26
pre_build() {
- sed -e 's|^\(encodings_DATA = $(DATA_FILES)\).*|\1|' -i Makefile
+ vsed -e 's|^\(encodings_DATA = $(DATA_FILES)\).*|\1|' -i Makefile
}
+
post_install() {
# encodings.dir are generated at pkg post-install time.
find ${DESTDIR} -name encodings.dir -delete
next reply other threads:[~2022-10-01 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 15:15 Duncaen [this message]
2022-10-02 1:13 ` [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-39591@inbox.vuxu.org \
--to=duncaen@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).