Github messages for voidlinux
 help / color / mirror / Atom feed
From: loreb <loreb@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] update xiate to new home and version
Date: Fri, 05 Nov 2021 16:01:38 +0100	[thread overview]
Message-ID: <20211105150138.PN2r5yWZrZDt6WC5r4mNV26ay2I7lGZolkOsDD7kZo8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33914@inbox.vuxu.org>

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

There is an updated pull request by loreb against master on the void-packages repository

https://github.com/loreb/void-packages xiate-new-home
https://github.com/void-linux/void-packages/pull/33914

update xiate to new home and version
This fixes https://github.com/void-linux/void-packages/issues/3549;
upstream is no longer using config.h, so we can simplify pre_configure.

<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [ X] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ X] I built this PR locally for my native architecture, (x86_64-musl)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->

I had to set $version to v21.05 (notice the extra 'v') because the tarball extracts to xiate-v21.05;
please let me know if there's a cleaner way.

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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-xiate-new-home-33914.patch --]
[-- Type: text/x-diff, Size: 1417 bytes --]

From ffff9ecc81fc54530960c2016cc6535f5c46aaf1 Mon Sep 17 00:00:00 2001
From: Lorenzo Beretta <vc.net.loreb@gmail.com>
Date: Fri, 5 Nov 2021 15:39:35 +0100
Subject: [PATCH] update xiate to new home and version

This fixes https://github.com/void-linux/void-packages/issues/3549;
upstream is no longer using config.h, so we can simplify pre_configure.
---
 srcpkgs/xiate/template | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/srcpkgs/xiate/template b/srcpkgs/xiate/template
index 742c53df8a8e..2958d7e5a96f 100644
--- a/srcpkgs/xiate/template
+++ b/srcpkgs/xiate/template
@@ -1,6 +1,6 @@
 # Template file for 'xiate'
 pkgname=xiate
-version=18.05
+version=v21.05
 revision=1
 build_style=gnu-makefile
 hostmakedepends="pkg-config"
@@ -9,12 +9,10 @@ short_desc="Terminal emulator which uses VTE as a backend"
 maintainer="Diogo Leal <diogo@diogoleal.com>"
 license="MIT"
 homepage="https://www.uninformativ.de/projects/xiate/"
-distfiles="https://github.com/vain/xiate/archive/v${version}.tar.gz"
-checksum=2f7317cc71849cdbf31479be224f9ed20fce25d2fa8320885a5294ed2101411b
+distfiles="https://www.uninformativ.de/git/xiate/archives/xiate-${version}.tar.gz"
+checksum=487dc53f48494e53a1db9aa36a1e04a594b207d7fcda84908e192bb4e706b7cb
 
 pre_configure() {
-	cp config.def.h config.h
-	[ -e ${FILESDIR}/config.h ] && cp ${FILESDIR}/config.h config.h
 	sed -i 's;/usr/local;/usr;g' Makefile
 }
 

  parent reply	other threads:[~2021-11-05 15:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05 14:49 [PR PATCH] " loreb
2021-11-05 14:58 ` [PR PATCH] [Updated] " loreb
2021-11-05 15:01 ` loreb [this message]
2021-11-05 15:08 ` loreb
2021-11-05 16:46 ` [PR REVIEW] " ericonr
2021-11-05 16:46 ` ericonr
2021-11-05 16:46 ` ericonr
2021-11-05 16:46 ` ericonr
2021-11-05 18:59 ` [PR PATCH] [Updated] " loreb
2021-11-05 19:02 ` loreb
2021-11-05 19:07 ` [PR PATCH] [Updated] " loreb
2021-11-05 19:10 ` loreb
2021-11-05 19:16 ` loreb
2021-11-14  6:58 ` ericonr
2021-11-14  6:58 ` ericonr
2021-11-14  6:58 ` [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=20211105150138.PN2r5yWZrZDt6WC5r4mNV26ay2I7lGZolkOsDD7kZo8@z \
    --to=loreb@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).