From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Re: jdupes-1.21.0-1
Date: Mon, 3 Oct 2022 22:13:46 +0200 [thread overview]
Message-ID: <d68e42ac-2783-03f2-cc30-f61986ce57c3@towo.net> (raw)
In-Reply-To: <f20554b4-e89b-37a0-35d2-70fbdeb39e52@kircheis.it>
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:
>>>
>>> https://github.com/jbruchon/jdupes/releases
>>>
>>> Federico
>> The help output mentions a manpage but there is none in the package.
>>
>
> Thank you for checking.
>
> I am not sure what the error could be.
> From my build folder:
>
> ----
> > tree .\jdupes\jdupes-1.21.0-1.x86_64\inst
> Folder PATH listing for volume Windows
> Volume serial number is 00000046 78D6:FE93
> C:\CYGPORT-PS\JDUPES\JDUPES-1.21.0-1.X86_64\INST
> ├───bin
> ├───share
> │ └───man
> │ └───man1
> └───usr
> ├───lib
> │ └───debug
> │ └───bin
> ├───share
> │ └───doc
> │ └───jdupes
> └───src
> └───debug
> └───jdupes-1.21.0-1
> > ls .\jdupes\jdupes-1.21.0-1.x86_64\inst\share\man\man1\
> jdupes.1
> ----
>
> I suppose that "jdupes.1" is the file that man shows to the end-user.
>
> Also from the makefile
>
> ----
> install: $(PROGRAM_NAME) installdirs
> $(INSTALL_PROGRAM) $(PROGRAM_NAME)
> $(DESTDIR)$(BIN_DIR)/$(PROGRAM_NAME)
> $(INSTALL_DATA) $(PROGRAM_NAME).1
> $(DESTDIR)$(MAN_DIR)/$(PROGRAM_NAME).$(MAN_EXT)
> ----
>
> 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/.
>
> 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.
next prev parent reply other threads:[~2022-10-03 20:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a19ffc66-81fa-d767-8d6b-e2c9a1a9667f@kircheis.it>
2022-10-03 18:25 ` Thomas Wolff
2022-10-03 19:25 ` Federico Kircheis
2022-10-03 20:13 ` Thomas Wolff [this message]
2022-10-03 20:24 ` Jon Turney
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=d68e42ac-2783-03f2-cc30-f61986ce57c3@towo.net \
--to=towo@towo.net \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).