Github messages for voidlinux
 help / color / mirror / Atom feed
From: drichline <drichline@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: diffuse-0.7.5
Date: Sun, 13 Nov 2022 03:53:13 +0100	[thread overview]
Message-ID: <20221113025313.S-Tv0R57SnZ1JxuIrR38bXlBdiyy0G0H_30Od4e3v14@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39971@inbox.vuxu.org>

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

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

https://github.com/drichline/void-packages diffuse-branch
https://github.com/void-linux/void-packages/pull/39971

New package: diffuse-0.7.5
Closes #39398 

#### 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**


#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
- I built this PR locally for these architectures:
  - aarch64-glibc

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

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

From 018b257e1dc75b3f0db30f1f2d94370003fb8a1f Mon Sep 17 00:00:00 2001
From: Dakota Richline <43507179+drichline@users.noreply.github.com>
Date: Sat, 15 Oct 2022 14:37:55 -0400
Subject: [PATCH] New package: diffuse-0.7.5

---
 srcpkgs/diffuse/template | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
 create mode 100644 srcpkgs/diffuse/template

diff --git a/srcpkgs/diffuse/template b/srcpkgs/diffuse/template
new file mode 100644
index 000000000000..5f05301ad2e3
--- /dev/null
+++ b/srcpkgs/diffuse/template
@@ -0,0 +1,14 @@
+# Template file for 'diffuse'
+pkgname=diffuse
+version=0.7.5
+revision=1
+build_style=meson
+hostmakedepends="gettext"
+makedepends="python3-cairo-devel python3-gobject-devel"
+depends="gtk+3 python3-gobject python3-cairo"
+short_desc="Graphical tool for merging and comparing text files"
+maintainer="Dakota Richline <drichline@protonmail.com>"
+license="GPL-2.0-only, FSFAP"
+homepage="https://github.com/MightyCreak/diffuse"
+distfiles="https://github.com/MightyCreak/diffuse/archive/refs/tags/v${version}.tar.gz"
+checksum=df34a7b2842956dc397d8e72f4d744dc50d403b515c5611f54bd137f3554eeb3

  parent reply	other threads:[~2022-11-13  2:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-15 18:43 [PR PATCH] " drichline
2022-10-19  2:06 ` [PR REVIEW] " abenson
2022-10-20  4:57 ` [PR PATCH] [Updated] " drichline
2022-10-20  4:58 ` [PR REVIEW] " drichline
2022-10-22 14:00 ` abenson
2022-11-04  7:27 ` drichline
2022-11-13  2:53 ` drichline [this message]
2022-11-13  2:53 ` drichline
2022-11-13  2:54 ` drichline
2022-11-14 22:38 ` [PR PATCH] [Merged]: " paper42

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=20221113025313.S-Tv0R57SnZ1JxuIrR38bXlBdiyy0G0H_30Od4e3v14@z \
    --to=drichline@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).