Github messages for voidlinux
 help / color / mirror / Atom feed
From: ifreund <ifreund@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] fcft: update to 2.5.1.
Date: Thu, 09 Dec 2021 21:41:18 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34449@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]

There is a new pull request by ifreund against master on the void-packages repository

https://github.com/ifreund/void-packages fcft
https://github.com/void-linux/void-packages/pull/34449

fcft: update to 2.5.1.
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](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/34449.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-fcft-34449.patch --]
[-- Type: text/x-diff, Size: 1270 bytes --]

From 7761bbf5c33302d993d5c3f4f4818a572c32a263 Mon Sep 17 00:00:00 2001
From: Isaac Freund <mail@isaacfreund.com>
Date: Thu, 9 Dec 2021 21:39:01 +0100
Subject: [PATCH] fcft: update to 2.5.1.

---
 srcpkgs/fcft/template | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/fcft/template b/srcpkgs/fcft/template
index e39da0ee4dde..4f78c6b67d07 100644
--- a/srcpkgs/fcft/template
+++ b/srcpkgs/fcft/template
@@ -1,10 +1,11 @@
 # Template file for 'fcft'
 pkgname=fcft
-version=2.5.0
+version=2.5.1
 revision=1
 wrksrc=$pkgname
 build_style=meson
-configure_args="-Drun-shaping=$(vopt_if textshaping enabled disabled)"
+configure_args="-Drun-shaping=$(vopt_if textshaping enabled disabled)
+ -Ddocs=enabled"
 hostmakedepends="pkg-config scdoc"
 makedepends="fontconfig-devel freetype-devel pixman-devel tllist
  $(vopt_if textshaping harfbuzz-devel)
@@ -14,7 +15,7 @@ maintainer="Isaac Freund <mail@isaacfreund.com>"
 license="MIT"
 homepage="https://codeberg.org/dnkl/fcft"
 distfiles="${homepage}/archive/${version}.tar.gz"
-checksum=58663c684f04154674c52551daa604618e0bb3db6c62492b06b13768fb4f4b3c
+checksum=1b9e9346c884f16bce9548806ea89c5e34ccc98ce27ec6ecff1f5011235de112
 
 build_options="textshaping"
 build_options_default="textshaping"

             reply	other threads:[~2021-12-09 20:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-09 20:41 ifreund [this message]
2021-12-11  2:22 ` [PR PATCH] [Merged]: " ericonr

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-34449@inbox.vuxu.org \
    --to=ifreund@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).