Github messages for voidlinux
 help / color / mirror / Atom feed
From: meator <meator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] duperemove: update to 0.13.
Date: Sat, 30 Sep 2023 15:26:29 +0200	[thread overview]
Message-ID: <20230930132629.vtrDP8xvWI8Ylab0EJJ8G2jZTOvdz5lLLWC1luzVAFw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46339@inbox.vuxu.org>

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

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

https://github.com/meator/void-packages duperemove
https://github.com/void-linux/void-packages/pull/46339

duperemove: update to 0.13.
<!-- Uncomment relevant sections and delete options which are not applicable -->
I have switched the template to `gnu-makefile` build style. The makefile looks well behaved regarding environmental variables, so I have set `make_use_env`. Hash files generated with the older release (most likely) won't be compatible with the new release. This is to be expected, the manpage and documentation say that the hash file format isn't stable.

#### Testing the changes
- I tested the changes in this PR: **YES**

ping mainainer: @Gottox 

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

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

From 6a57f2c9bf575db8bf9c9739b0491c22836607d5 Mon Sep 17 00:00:00 2001
From: meator <meator.dev@gmail.com>
Date: Sat, 30 Sep 2023 14:55:50 +0200
Subject: [PATCH] duperemove: update to 0.13.

---
 srcpkgs/duperemove/patches/add_dev_t_include.patch | 11 +++++++++++
 srcpkgs/duperemove/template                        | 14 ++++++--------
 2 files changed, 17 insertions(+), 8 deletions(-)
 create mode 100644 srcpkgs/duperemove/patches/add_dev_t_include.patch

diff --git a/srcpkgs/duperemove/patches/add_dev_t_include.patch b/srcpkgs/duperemove/patches/add_dev_t_include.patch
new file mode 100644
index 0000000000000..7556bf8eebeaf
--- /dev/null
+++ b/srcpkgs/duperemove/patches/add_dev_t_include.patch
@@ -0,0 +1,11 @@
+--- a/dbfile.h
++++ b/dbfile.h
+@@ -7,6 +7,8 @@
+ #include <stdbool.h>
+ #include "util.h"
+ 
++#include <sys/types.h>
++
+ struct filerec;
+ struct block_csum;
+ struct extent_csum;
diff --git a/srcpkgs/duperemove/template b/srcpkgs/duperemove/template
index 22d41bdf4ec47..9678fdff9393d 100644
--- a/srcpkgs/duperemove/template
+++ b/srcpkgs/duperemove/template
@@ -1,7 +1,9 @@
 # Template file for 'duperemove'
 pkgname=duperemove
-version=0.11.2
+version=0.13
 revision=1
+build_style=gnu-makefile
+make_use_env=yes
 hostmakedepends="pkg-config"
 makedepends="sqlite-devel libglib-devel libgcrypt-devel"
 short_desc="Tools for deduping file systems"
@@ -9,11 +11,7 @@ maintainer="Enno Boland <gottox@voidlinux.org>"
 license="GPL-2.0-only"
 homepage="https://github.com/markfasheh/duperemove"
 distfiles="https://github.com/markfasheh/duperemove/archive/v${version}.tar.gz"
-checksum=e162c2cf99c9d1e1e111cf84fa2615490a7d654173a3719651a962257bf8179e
+checksum=65fc972339965976cf617ed430ece86dc64c2695b2017db058413aa098f1da89
 
-do_build() {
-	make CC=$CC CFLAGS="$CFLAGS $LDFLAGS -fcommon"
-}
-do_install() {
-	make PREFIX=/usr SBINDIR=/usr/bin DESTDIR=${DESTDIR} install
-}
+# The makefile tries to use git to guess if these aren't set.
+export VERSION="${version}" IS_RELEASE=1

  reply	other threads:[~2023-09-30 13:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-30 13:04 [PR PATCH] " meator
2023-09-30 13:26 ` meator [this message]
2023-09-30 13:41 ` meator
2023-10-01  4:35 ` [PR PATCH] [Merged]: " classabbyamp

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=20230930132629.vtrDP8xvWI8Ylab0EJJ8G2jZTOvdz5lLLWC1luzVAFw@z \
    --to=meator@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).