Github messages for voidlinux
 help / color / mirror / Atom feed
From: omar-polo <omar-polo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] got: update to 0.83
Date: Sun, 05 Feb 2023 10:27:41 +0100	[thread overview]
Message-ID: <20230205092741.YOFx1rhKoXEeap85s4v4pGWN5oWfPgta9AAYX0DdwIY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42089@inbox.vuxu.org>

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

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

https://github.com/omar-polo/void-packages got/0.83
https://github.com/void-linux/void-packages/pull/42089

got: update to 0.83
#### Testing the changes
- I tested the changes in this PR: **YES**

#### Local build testing
- I built this PR locally for my native architecture, (amd64-musl)

I had to disable cross-compiling.  since 0.79 there's a subproject `template` that is needed to generate some sources during build time.  it needs to be compiled and executed on the host.  However, as a byproduct of the build of `template`, some object files are left in places where they're then picked up by the regular build which thus fails at linking.  Will try to have it fixed for the next release.


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

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

From 92cc6051c38e4124d0158ffa514af123de9a022f Mon Sep 17 00:00:00 2001
From: Omar Polo <op@omarpolo.com>
Date: Thu, 19 Jan 2023 19:24:43 +0100
Subject: [PATCH] got: update to 0.83

---
 srcpkgs/got/template | 11 +++++++++--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/got/template b/srcpkgs/got/template
index b41834246727..62c1feebc9c6 100644
--- a/srcpkgs/got/template
+++ b/srcpkgs/got/template
@@ -1,6 +1,6 @@
 # Template file for 'got'
 pkgname=got
-version=0.79
+version=0.83
 revision=1
 build_style=gnu-configure
 hostmakedepends="byacc pkg-config"
@@ -11,7 +11,14 @@ license="ISC"
 homepage="https://gameoftrees.org"
 changelog="https://gameoftrees.org/releases/CHANGES"
 distfiles="https://gameoftrees.org/releases/portable/got-portable-${version}.tar.gz"
-checksum="78be1c0a905184ed1cb506468359faf87e4ee86851291b1670439c46bfb3d87c"
+checksum="90d854e8e47d21434f2fbd83f749e1ab65f9be6556ed8526a67abf10e52f1bff"
+nocross="the template subproject needs to be compiled and executed on the host but produces object files that are used by the cross build."
+
+post_extract() {
+	# XXX: doesn't correctly link to libbsd; will be fixed for the next release
+	(cd template && \
+		sed -i.orig 's,sys/queue.h,bsd/sys/queue.h,g' configure parse.[cy])
+}
 
 post_install() {
 	sed -n '/Copyright/,/PERFORMANCE/p' got/got.c > LICENSE

  reply	other threads:[~2023-02-05  9:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-05  9:23 [PR PATCH] " omar-polo
2023-02-05  9:27 ` omar-polo [this message]
2023-02-05  9:49 ` paper42
2023-02-24  8:52 ` [PR PATCH] [Closed]: " omar-polo
2023-02-24  8:52 ` omar-polo

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=20230205092741.YOFx1rhKoXEeap85s4v4pGWN5oWfPgta9AAYX0DdwIY@z \
    --to=omar-polo@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).