From: Spacur <Spacur@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: libpurple-discord-0.9.2023.02.15.git.4a09188
Date: Sat, 24 Jun 2023 14:30:04 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44608@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1660 bytes --]
There is a new pull request by Spacur against master on the void-packages repository
https://github.com/Spacur/void-packages libpurple-discord
https://github.com/void-linux/void-packages/pull/44608
New package: libpurple-discord-0.9.2023.02.15.git.4a09188
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Description
Discord plugin for libpurple
#### Testing the changes
- I tested the changes in this PR: **YES**
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
#### Local build testing
- I built this PR locally for my native architecture: **x86_64**
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- i686 (crossbuild)
- armv6l (crossbuild)
- armv7l (crossbuild)
#### Notes
- Has been tested on x86_64 and appears to be working fine at runtime (with pidgin) over the course of several days, however no testing has been made for alternative architectures/musl despite successful builds.
- Authors have never provided versions/releases, latest git commit at the time of writing is being used instead.
A patch file from https://github.com/void-linux/void-packages/pull/44608.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libpurple-discord-44608.patch --]
[-- Type: text/x-diff, Size: 1217 bytes --]
From 647c2ef23e776c4863bbb615fff84afd33c89e00 Mon Sep 17 00:00:00 2001
From: Spark <sparksman@disroot.org>
Date: Sat, 24 Jun 2023 12:43:54 +0000
Subject: [PATCH] New package: libpurple-discord-0.9.2023.02.15.git.4a09188
---
srcpkgs/libpurple-discord/template | 13 +++++++++++++
1 file changed, 13 insertions(+)
create mode 100644 srcpkgs/libpurple-discord/template
diff --git a/srcpkgs/libpurple-discord/template b/srcpkgs/libpurple-discord/template
new file mode 100644
index 000000000000..62252791d0f1
--- /dev/null
+++ b/srcpkgs/libpurple-discord/template
@@ -0,0 +1,13 @@
+# Template file for 'libpurple-discord'
+pkgname=libpurple-discord
+version=0.9.2023.02.15.git.4a09188
+revision=1
+build_style=gnu-makefile
+hostmakedepends="pkg-config ImageMagick gettext"
+makedepends="json-glib-devel libpurple-devel nss-devel qrencode-devel"
+short_desc="Discord plugin for libpurple"
+maintainer="Spark <sparksman@disroot.org>"
+license="GPL-2.0-or-later"
+homepage="https://github.com/EionRobb/purple-discord"
+distfiles="https://github.com/EionRobb/purple-discord/tarball/4a091883e646f2c103ae68c41d04b1b880e8d0bf>purple-discord.tar.gz"
+checksum=4f462facf18d200f7ff9f4c3e96f6a6b95f6c13f553d343c91eb861d1b2bebdd
next reply other threads:[~2023-06-24 12:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-24 12:30 Spacur [this message]
2023-06-24 18:21 ` abenson
2023-06-24 21:15 ` Spacur
2023-06-26 19:25 ` classabbyamp
2023-06-28 21:57 ` Spacur
2023-06-28 21:57 ` [PR PATCH] [Closed]: " Spacur
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-44608@inbox.vuxu.org \
--to=spacur@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).