Github messages for voidlinux
 help / color / mirror / Atom feed
From: Vaelatern <Vaelatern@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: netrek-client-cow-3.3.1
Date: Sun, 17 May 2020 05:37:55 +0200	[thread overview]
Message-ID: <20200517033755.drrEP2Q3Kb-rSR9SJH9A_S3Q1G_RV4OBVJky_q2XRuQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21853@inbox.vuxu.org>

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

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

https://github.com/Vaelatern/void-packages netrek
https://github.com/void-linux/void-packages/pull/21853

New package: netrek-client-cow-3.3.1
With some people being very bored, they might like having this packaged.

It doesn't build. Upstream is active.

The patch is changes between the packaged release and now, I filed a bug with upstream (but since it fails to build from source, that might have been premature). https://github.com/quozl/netrek-client-cow/issues/2

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

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

From 5a05c7e243ef20b417081e9e87ae4c857c4614dd Mon Sep 17 00:00:00 2001
From: Toyam Cox <Vaelatern@voidlinux.org>
Date: Mon, 11 May 2020 19:18:26 -0400
Subject: [PATCH] New package: netrek-client-cow-3.3.1

---
 srcpkgs/netrek-client-cow/template | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)
 create mode 100644 srcpkgs/netrek-client-cow/template

diff --git a/srcpkgs/netrek-client-cow/template b/srcpkgs/netrek-client-cow/template
new file mode 100644
index 00000000000..0b03107be2e
--- /dev/null
+++ b/srcpkgs/netrek-client-cow/template
@@ -0,0 +1,29 @@
+# Template file for 'netrek-client-cow'
+pkgname=netrek-client-cow
+version=3.3.2
+revision=1
+build_style=gnu-configure
+hostmakedepends="libtool automake"
+makedepends="libX11-devel imlib2-devel libXxf86vm-devel gmp-devel
+ SDL_mixer-devel SDL-devel libXpm-devel"
+short_desc="Netrek Client (C and X11)"
+maintainer="Toyam Cox <Vaelatern@voidlinux.org>"
+license="MIT, custom"
+homepage="https://www.netrek.org/"
+distfiles="https://www.netrek.org/files/COW/netrek-client-cow-${version}.tar.gz"
+checksum=cac219248d71033b62098c3da1ca6b4408974b22996da39eaba213b2253e6da3
+
+post_install() {
+	vlicense COPYING
+	vlicense copyright.h
+	vlicense copyright2.h
+	ln -s ../bin/netrek-client-cow usr/games/netrek-client-cow
+}
+
+do_check() {
+	echo "Broken"
+}
+
+# REMARKS:
+# Source tracked at https://github.com/quozl/netrek-client-cow
+# Custom is a sort of public domain declaration

  parent reply	other threads:[~2020-05-17  3:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-11 23:26 [PR PATCH] " Vaelatern
2020-05-11 23:32 ` [PR PATCH] [Updated] " Vaelatern
2020-05-17  3:37 ` Vaelatern [this message]
2020-05-17  3:38 ` Vaelatern
2020-05-21 21:43 ` Vaelatern
2020-05-22  3:13 ` Vaelatern
2020-05-22  3:13 ` Vaelatern

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=20200517033755.drrEP2Q3Kb-rSR9SJH9A_S3Q1G_RV4OBVJky_q2XRuQ@z \
    --to=vaelatern@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).