Am Tue, Jan 30, 2024 at 06:07:49PM +0000 schrieb Stuart Henderson:
> On 2024/01/30 19:05, Björn Ketelaars wrote:
> > On Sun 28/01/2024 07:18, Martin Ziemer wrote:
> > > This patch updates fdupes from 2.2.1 to 2.3.0.
> > > 
> > > Tested on amd64.
> > 
> > This update picks up sqlite3 [0]. If this is intended then you need to
> > add sqlite3 to WANTLIB and databases/sqlite3 to LIB_DEPENDS.
> > Alternatively you could set CONFIGURE_ARGS+= --without-sqlite.
> > 
> > [0] 
> > https://github.com/adrianlopezroche/fdupes/commit/ab5ef95e2b2633d0ca1a5ae0b8ac41abde160100
> 
> The sqlite cache seems useful to me.
I agree.

The diff below has the two changes from Björn Ketelaars included.

Index: Makefile
===================================================================
RCS file: /cvs/ports/sysutils/fdupes/Makefile,v
retrieving revision 1.17
diff -u -p -r1.17 Makefile
--- Makefile    27 Sep 2023 17:16:25 -0000      1.17
+++ Makefile    30 Jan 2024 19:01:28 -0000
@@ -1,6 +1,6 @@
 COMMENT=       identify or delete duplicate files
 
-V=             2.2.1
+V=             2.3.0
 DISTNAME=      fdupes-$V
 CATEGORIES=    sysutils
 
@@ -12,11 +12,12 @@ MAINTAINER =        Martin Ziemer <horrad@horra
 # MIT
 PERMIT_PACKAGE=        Yes
 
-WANTLIB += c curses pcre2-32
+WANTLIB += c curses pcre2-32 sqlite3
 
 CONFIGURE_STYLE= gnu
 CONFIGURE_ENV= CPPFLAGS="-I${LOCALBASE}/include" LDFLAGS="-L${LOCALBASE}/lib"
 
-LIB_DEPENDS=   devel/pcre2
+LIB_DEPENDS=   devel/pcre2 \
+               databases/sqlite3
 
 .include <bsd.port.mk>
Index: distinfo
===================================================================
RCS file: /cvs/ports/sysutils/fdupes/distinfo,v
retrieving revision 1.7
diff -u -p -r1.7 distinfo
--- distinfo    9 Sep 2022 12:11:19 -0000       1.7
+++ distinfo    30 Jan 2024 19:01:28 -0000
@@ -1,2 +1,2 @@
-SHA256 (fdupes-2.2.1.tar.gz) = hGu3nKPwFXhWqpPtULSSF/62jhs1ImGTtrxXi+DFaY0=
-SIZE (fdupes-2.2.1.tar.gz) = 144719
+SHA256 (fdupes-2.3.0.tar.gz) = YXDWSn5WXuMUzKTdJaEj5gqh4/67EeVweL67nB2n4Bk=
+SIZE (fdupes-2.3.0.tar.gz) = 154700

Reply via email to