Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 26 Feb 2025 15:00:00 +0000
From:      Alexey Dokuchaev <danfe@freebsd.org>
To:        Guido Falsi <madpilot@freebsd.org>
Cc:        ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org
Subject:   Re: git: 0d316feccaf8 - main - sysutils/cpdup-FreeBSD: Add FreeBSD fork of cpdup
Message-ID:  <Z78scMZnnQcnFeDI@FreeBSD.org>
In-Reply-To: <0a1df7c1-e4ad-4439-b4ac-376f18ed50cc@FreeBSD.org>
References:  <202502252200.51PM0JNl002582@gitrepo.freebsd.org> <Z76STq6XHJHpVxMH@FreeBSD.org> <0a1df7c1-e4ad-4439-b4ac-376f18ed50cc@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 26, 2025 at 08:41:49AM +0100, Guido Falsi wrote:
> On 26/02/25 05:02, Alexey Dokuchaev wrote:
> > On Tue, Feb 25, 2025 at 10:00:19PM +0000, Guido Falsi wrote:
> > > commit 0d316feccaf89c1bd804d6001274426a7135c93a
> > > 
> > >    sysutils/cpdup-FreeBSD: Add FreeBSD fork of cpdup
> > > 
> > >    Add a fork of cpdup, including patches to support copy_file_range(2)
> > >    and allowing to choose checksum algorithm.
> > 
> > Any reason not to add this to the `sysutils/cpdup' itself?  If there are
> > fears it might break something or be not fit for other reasons, it can be
> > hidden under option.
> 
> These are actually separate projects at this point, users should be well
> aware they are using a fork and able to choose which one to use.

Okay, but then the fork's name is poorly chosen: as a FreeBSD user I'd be
rather confused as to why there are two FreeBSD ports, similarly named but
one has explicit -FreeBSD suffix (note that this is quite unconventional
on its own, not to mention the port/package name uglification it entails).

> Building two separate projects [...] with different names

Well, the *name* is actually the same.

> coming from different repositories and version numbers from the same port
> depending on an option looks even more strange to me.

Oh, I see, so it's fucked up on all sides, not just ours.  Let's hope both
upstreams, DragonFly's and ours, can sort this out so we don't have to keep
two pretty much identical ports in the tree. :-/

./danfe



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Z78scMZnnQcnFeDI>