Github messages for voidlinux
 help / color / mirror / Atom feed
From: meator <meator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] st: update to 0.9.
Date: Sat, 22 Oct 2022 14:30:38 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40105@inbox.vuxu.org> (raw)

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

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

https://github.com/meator/void-packages st
https://github.com/void-linux/void-packages/pull/40105

st: update to 0.9.
<!-- 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 [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/40105.patch is attached

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

From 894cd9a692824306a8ce23316c43072a974c6174 Mon Sep 17 00:00:00 2001
From: meator <meator.dev@gmail.com>
Date: Sat, 22 Oct 2022 14:24:38 +0200
Subject: [PATCH] st: update to 0.9.

---
 srcpkgs/st/template | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/st/template b/srcpkgs/st/template
index e6d7e3beb977..0acd0bb45bf5 100644
--- a/srcpkgs/st/template
+++ b/srcpkgs/st/template
@@ -1,7 +1,7 @@
 # Template file for 'st'
 pkgname=st
-version=0.8.5
-revision=2
+version=0.9
+revision=1
 build_style=gnu-makefile
 make_use_env=compliant
 hostmakedepends="pkg-config"
@@ -12,10 +12,10 @@ maintainer="meator <meator.dev@gmail.com>"
 license="MIT"
 homepage="https://st.suckless.org"
 distfiles="https://dl.suckless.org/${pkgname}/${pkgname}-${version}.tar.gz"
-checksum=ea6832203ed02ff74182bcb8adaa9ec454c8f989e79232cb859665e2f544ab37
+checksum=f36359799734eae785becb374063f0be833cf22f88b4f169cd251b99324e08e7
 
 pre_build() {
-	sed -i 's|Liberation Mono|Monospace|g' config.def.h
+	vsed -i config.def.h -e 's|Liberation Mono|Monospace|g'
 	[ -e ${FILESDIR}/config.h ] && cp ${FILESDIR}/config.h config.h
 	mkdir -p ${DESTDIR}/usr/share/terminfo
 }
@@ -26,6 +26,7 @@ pre_install() {
 
 post_install() {
 	vdoc README
+	vdoc FAQ
 	vlicense LICENSE
 }
 

             reply	other threads:[~2022-10-22 12:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-22 12:30 meator [this message]
2022-10-22 20:19 ` [PR PATCH] [Merged]: " paper42

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