public inbox for
 help / color / mirror / Atom feed
From: Federico Kircheis <>
To: cygwin <>
Subject: [ITP] jdupes
Date: Tue, 13 Sep 2022 20:24:44 +0200	[thread overview]
Message-ID: <> (raw)

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

Hello to everyone,

I'm interested in becoming a package maintainer for the program jdupes.

It would be a new package for the cygwin distribution, but it is already
distributed on different systems.
For example

The current release can be downloaded from

and can be compiled on cygwin without patches (necessary changes have 
been integrated by the author after contacting him).

jdupes has a native windows port, but I see an added value having it 
available in cygwin.

It is a program similar to fdupes (already present in cygwin), and is 
not a drop-in replacement. From the website description:

 > Why use jdupes instead of the original fdupes or other duplicate finders?
 > The biggest reason is raw speed. In testing on various data sets, 
jdupes is over 7 times faster than fdupes-1.51 on average.

.hint and .cygport files are attached

Best regards


[-- Attachment #2: jdupes.cygport --]
[-- Type: text/plain, Size: 595 bytes --]

# jdupes.cygport
SUMMARY="jdupes is a program for identifying and taking actions upon duplicate files."
DESCRIPTION="jdupes is a program for identifying and taking actions upon duplicate files."



src_compile() {
	cd ${B}

	NO_WINDOWS=1 cygmake "PREFIX=${D}"

	cd ${B}
	NO_WINDOWS=1 cygmake "PREFIX=${D}" install

[-- Attachment #3: jdupes.hint --]
[-- Type: text/plain, Size: 433 bytes --]

# jdupes.hint
sdesc: "jdupes is a program for identifying and taking actions upon duplicate files"
ldesc: "Searches the given path(s) for duplicate files.
Such files are found by comparing file sizes, then partial and full file hashes, followed by a byte-by-byte comparison.
The default behavior with no other <action options> specified (delete, summarize, link, dedupe, etc.) is to print sets of matching files."

category: Utility

                 reply	other threads:[~2022-09-13 18:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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 read-only IMAP folder(s) and NNTP newsgroup(s).