Github messages for voidlinux
 help / color / mirror / Atom feed
From: daniel-eys <daniel-eys@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] srain: update to 1.0.2.
Date: Sun, 12 Apr 2020 17:02:39 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20920@inbox.vuxu.org> (raw)

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

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

https://github.com/daniel-eys/void-packages srain
https://github.com/void-linux/void-packages/pull/20920

srain: update to 1.0.2.
cross patch got upstreamed.

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

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

From a213548ec5b169874f64c286e01e14245385a6d3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Daniel=20Ey=C3=9Fer?= <daniel.eysser@gmail.com>
Date: Sun, 12 Apr 2020 16:01:45 +0200
Subject: [PATCH] srain: update to 1.0.2.

---
 srcpkgs/srain/patches/fix-cross.patch | 13 -------------
 srcpkgs/srain/template                |  9 +++++----
 2 files changed, 5 insertions(+), 17 deletions(-)
 delete mode 100644 srcpkgs/srain/patches/fix-cross.patch

diff --git a/srcpkgs/srain/patches/fix-cross.patch b/srcpkgs/srain/patches/fix-cross.patch
deleted file mode 100644
index 05e640a4679..00000000000
--- a/srcpkgs/srain/patches/fix-cross.patch
+++ /dev/null
@@ -1,13 +0,0 @@
---- src/Makefile~	2020-03-15 17:22:29.077747681 +0100
-+++ src/Makefile	2020-03-15 17:22:32.599747681 +0100
-@@ -3,7 +3,9 @@
- # Complie C source codes and output object files to $(BUILD_DIR), then links
- # them together to get a executable $(TARGET).
- 
--CC = gcc
-+ifeq "$(origin CC)" "default"
-+	CC = gcc
-+endif
- DEFS = -D PACKAGE='"$(PACKAGE)"' \
- 	   -D PACKAGE_NAME='"$(PACKAGE_NAME)"' \
- 	   -D PACKAGE_VERSION='"$(PACKAGE_VERSION)"' \
diff --git a/srcpkgs/srain/template b/srcpkgs/srain/template
index 3679e2679e3..a50d1c2fd4e 100644
--- a/srcpkgs/srain/template
+++ b/srcpkgs/srain/template
@@ -1,15 +1,16 @@
 # Template file for 'srain'
 pkgname=srain
-version=1.0.1
+version=1.0.2
 revision=1
 build_style=configure
 build_helper=gir
-configure_args="--prefix=/usr"
+configure_args="--prefix=/usr --sysconfdir=/etc"
 hostmakedepends="pkg-config gettext glib-devel"
-makedepends="glib-devel gtk+3-devel libconfig-devel libressl-devel libsecret-devel libsoup-devel"
+makedepends="glib-devel gtk+3-devel libconfig-devel libressl-devel
+ libsecret-devel libsoup-devel"
 short_desc="Modern IRC client written in GTK"
 maintainer="avoidr <avoidr@firemail.cc>"
 license="GPL-3.0-only"
 homepage="https://srain.im/"
 distfiles="https://github.com/SrainApp/srain/archive/${version}.tar.gz"
-checksum=104d0b56944b9eabed9ada7bbca28df4b0dedb972e67fa533079dcf5bde35254
+checksum=ecc8d5b1bfb7e72e8310f888a34415b66d4aa4da752776a4d46828c354844fc2

             reply	other threads:[~2020-04-12 15:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-12 15:02 daniel-eys [this message]
2020-04-12 15:35 ` [PR PATCH] [Merged]: " xtraeme

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-20920@inbox.vuxu.org \
    --to=daniel-eys@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).