Re: x-to-1

On Sat, 11 Feb 2023 at 09:05, Bruno Haible wrote: > The package name doesn't change that often. (Although, for 'recode', it > already changed 3 times: recode → GNU recode → Free recode → recode.) > It may just be me, but I've renamed packages myself often enough, and then failed to find particul

Re: x-to-1

Reuben Thomas wrote: > it avoids repeating the name of the package. The package name doesn't change that often. (Although, for 'recode', it already changed 3 times: recode → GNU recode → Free recode → recode.) Bruno

Re: x-to-1

On Sat, 11 Feb 2023 at 08:48, Bruno Haible wrote: > I got the impression that without a .x file, the NAME section of the output > is too silly. > > This is correct, but although (as you observe) this means that some documentation goes in the Makefile.am, it avoids repeating the name of the packag

Re: x-to-1

Reuben Thomas wrote: > There's one final thing that would be useful for > recode: to make the .x file optional. Recode (unlike all the other programs > I use with help2man) does not need any extra information. I tried simply > creating an empty .x file, but help2man gives an error. I got the impre

Re: x-to-1

On Thu, 9 Feb 2023 at 02:49, Bruno Haible wrote: > > > > In general, then, it would be good if x-to-1 ignored unknown options and > > passed them to help2man; would that be possible? > > Passing down additional options to help2man is a very good idea; > implemente

Re: x-to-1

ction that uses a \*['] sequence, but > that seems a shame. > > 2. Similarly, I passed a --name option, which avoids having to repeat the > name of the program in a .x file's NAME section. > > In general, then, it would be good if x-to-1 ignored unknown options and > passed th

Re: x-to-1

Reuben Thomas wrote: > It would be good to document that x-to-1 needs CROSS_COMPILING and PERL set > up by configure.ac. Or perhaps it's worth a gnulib module? Good point. I think putting these tests into a Gnulib module 'x-to-1' would not be the right approach, because - t

x-to-1

ion, which avoids having to repeat the name of the program in a .x file's NAME section. In general, then, it would be good if x-to-1 ignored unknown options and passed them to help2man; would that be possible? It would be good to document that x-to-1 needs CROSS_COMPILING and PERL set up by c

x-to-1: restore ability to use original calling convention

In <https://lists.gnu.org/archive/html/bug-gnulib/2012-12/msg00053.html> Alexandre Duret-Lutz did an incompatible change to the x-to-1 script: The expected calling convention was to pass a HELP2MAN argument of the form '/usr/bin/perl -w -- help2man'. After his change, the scr

x-to-1: avoid failure due to missing perl modules

help2man line 29. *** Error 1 in gettext-runtime/man (Makefile:1660 'gettext.1.in') This patch avoids the failure, leading to a message "WARNING: The man page gettext.1.in cannot be updated yet." - and the build continues. 2019-04-13 Bruno Haible x-to-1: Avoid

Re: [PATCH] x-to-1: Honor $PERL

Jim Meyering wrote: ... > That looks like a fine patch. > It looks like this is Bruno's script, but it's small/safe enough > that if there's no objection by tomorrow, I'll push it then. Thanks again. Pushed.

Re: [PATCH] x-to-1: Honor $PERL

Alexandre Duret-Lutz wrote: > * build-aux/x-to-1.in: Run $HELP2MAN via $PERL so that the user gets a > chance to use his preferred version of Perl. This is typically > required by Darwin users whose default /usr/bin/perl do not have all > the libraries required by help2man, and who

[PATCH] x-to-1: Honor $PERL

* build-aux/x-to-1.in: Run $HELP2MAN via $PERL so that the user gets a chance to use his preferred version of Perl. This is typically required by Darwin users whose default /usr/bin/perl do not have all the libraries required by help2man, and who need to use their MacPorts installation of Perl

Re: new file: x-to-1.in

Simon Josefsson wrote: > It wasn't clear to me that a '.x skeleton' was the help2man --include > file before reading the script. Maybe add something like this? > > The .x skeleton is the file that is passed to help2man --include, > and the file should follow the format described in the help2m

Re: new file: x-to-1.in

Bruno Haible <[EMAIL PROTECTED]> writes: > Hi, > > This script that generates man pages using help2man appears to be useful > outside gettext; I'm therefore adding it to gnulib. ... > # This program creates a program's manual from the .x skeleton and its --help > # output. It wasn't clear to me t

new file: x-to-1.in

Hi, This script that generates man pages using help2man appears to be useful outside gettext; I'm therefore adding it to gnulib. 2006-08-22 Bruno Haible <[EMAIL PROTECTED]> * build-aux/x-to-1.in: New file, from GNU gettext. == build-au