Github messages for voidlinux
 help / color / mirror / Atom feed
From: dotnetfox <dotnetfox@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] xst: fix terminfo and TERM name in Xresources
Date: Thu, 17 Dec 2020 17:57:45 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27233@inbox.vuxu.org> (raw)

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

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

https://github.com/dotnetfox/void-packages xst
https://github.com/void-linux/void-packages/pull/27233

xst: fix terminfo and TERM name in Xresources
Fixes "unknown capability" during terminfo generation and removes replacing TERM name in xresources since it is unneeded anymore.

The previous pull request is messed up by me because of lacking knowledge about git.

Please excuse me for such a move.

A patch file from https://github.com/void-linux/void-packages/pull/27233.patch is attached

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

From f15894ff3f0f77a59f957f45195d7baf4c16cce0 Mon Sep 17 00:00:00 2001
From: Ranme Fritzvilliams <me@dotnetfox.tk>
Date: Thu, 17 Dec 2020 19:53:34 +0300
Subject: [PATCH] xst: fix terminfo and TERM name in Xresources

INSTALL: allow tic compile with custom-defined variables such as rmxx,
smxx, Tc, Ms, Se, Ss.

Fixes "unknown capability" error caused by custom
variables added in the upstream code since the release 0.8.4.

template: replacing st-256color to xst-256color became unnecessary since
it has been fixed in the upstream code.

Leaving it as is will change "xst-256color" to "xxst-256color".
---
 srcpkgs/xst/INSTALL  | 2 +-
 srcpkgs/xst/template | 3 +--
 2 files changed, 2 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/xst/INSTALL b/srcpkgs/xst/INSTALL
index c73ae7337bb..fcad0563b68 100644
--- a/srcpkgs/xst/INSTALL
+++ b/srcpkgs/xst/INSTALL
@@ -1,5 +1,5 @@
 case "${ACTION}" in
 post)
-	tic -s usr/share/terminfo/x/xst.terminfo
+	tic -sx usr/share/terminfo/x/xst.terminfo
 	;;
 esac
diff --git a/srcpkgs/xst/template b/srcpkgs/xst/template
index b3743d1547d..8600c680ae3 100644
--- a/srcpkgs/xst/template
+++ b/srcpkgs/xst/template
@@ -1,7 +1,7 @@
 # Template file for 'xst'
 pkgname=xst
 version=0.8.4.1
-revision=1
+revision=2
 build_style=gnu-makefile
 make_use_env=compliant
 hostmakedepends="pkg-config"
@@ -21,7 +21,6 @@ do_install() {
 	vinstall st.info 644 usr/share/terminfo/x xst.terminfo
 	vdoc README
 	vdoc FAQ
-	vsed -i 's/st-256color/xst-256color/' .Xresources
 	vdoc .Xresources Xresources
 	vlicense LICENSE
 }

             reply	other threads:[~2020-12-17 16:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17 16:57 dotnetfox [this message]
2020-12-17 18:03 ` [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-27233@inbox.vuxu.org \
    --to=dotnetfox@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).