public inbox for
 help / color / mirror / Atom feed
From: Jon Turney <>
To: Federico Kircheis <>,
	The Cygwin Mailing List <>
Subject: Re: [ANNOUNCEMENT] Re: jdupes-1.21.0-1
Date: Mon, 3 Oct 2022 21:24:37 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 03/10/2022 21:13, Thomas Wolff wrote:
> Am 03.10.2022 um 21:25 schrieb Federico Kircheis:
>> On 10/3/22 20:25, Thomas Wolff wrote:
>>> Am 02.10.2022 um 23:27 schrieb Federico Kircheis:
>>>> Version 1.21.0-1 of jdupes has been uploaded.
>>>> jdupes is a program for finding and acting on duplicate files
>>>> On GitHub it is possible to find the changelog for the new release:
>>>> Federico
>>> The help output mentions a manpage but there is none in the package.

I think the jdupes.1 manpage is in the package, but it's not installed 
in a location where man is going to look for it.

>> I suppose that "jdupes.1" is the file that man shows to the end-user.
>> Also from the makefile
>> ----
>> install: $(PROGRAM_NAME) installdirs
>>     $(INSTALL_DATA)        $(PROGRAM_NAME).1 
>> ----
>> and in the cygport file I do a cygmake install...
>> Could it be that "jdupes.1" should go in another directory?
> It should go into /usr/share/man/man1/.

Yes, the fact that /usr is omitted suggests MAN_DIR isn't being set 
correctly by that Makefile.

>> I am not familiar with man pages (as developer)
> I am not really familiar with cygport, sorry. It needs trial-and-error 
> in my experience.

Solving problems by thinking about them is usually much more efficient 
than a thud-and-blunder approach.

      reply	other threads:[~2022-10-03 20:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2022-10-03 18:25 ` Thomas Wolff
2022-10-03 19:25   ` Federico Kircheis
2022-10-03 20:13     ` Thomas Wolff
2022-10-03 20:24       ` Jon Turney [this message]

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).