linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Brian.Inglis@Shaw.ca, linux-man@vger.kernel.org
Cc: Deri <deri@chuzzlewit.myzen.co.uk>
Subject: Re: No 6.05/.01 pdf book available
Date: Sat, 12 Aug 2023 02:02:49 +0200	[thread overview]
Message-ID: <ac4a6675-f96a-cf39-f2c9-381d6ce0733b@kernel.org> (raw)
In-Reply-To: <01d3855b-65dc-8b99-83cf-ebe1f97a2d83@Shaw.ca>


[-- Attachment #1.1: Type: text/plain, Size: 2649 bytes --]

Hi Brian,

On 2023-08-07 18:21, Brian Inglis wrote:
[...]

>>> $ pwd
>>> /home/alx/src/linux/man-pages/man-pages/6.04/scripts/LinuxManBook
>>> $ ./BuildLinuxMan.pl  ../../
>>> [...]
>>> Failed to open 'DESC'
> 
> That annoyingly minimal message provoked the patch submitted.

Yeah; it took me some time to find the cause.  The error message doesn't
even tell who failed --was it the shell, was it gropdf, was it troff?--.

:)

> 
>>>> When I run the script/LinuxManBook/BuildLinuxMan.pl, after applying the gropdf
>>>> patch, manually in the build dir, I get a pdf, but without any man page footers.
> 
>>> Hmm, that's weird.  After applying your patch, It works fine for me.
>>> I do see the page footers.  However, I have old builds of groff in my
>>> system, which I haven't cleaned up, so maybe they interfere positively
>>> to that outcome.  Maybe from a clean installation of Debian Sid I
>>> wouldn't be able to reproduce that.
> 
>> I have uploaded the 6.05.01 book now.
> 
> Nice - with current page footers!

Can you confirm if you can build the book correctly after I pushed Deri's
change?  I'm worried that I couldn't reproduce your problem, and would
like to know if it has gone away or persists for you.

> 
>>> Nevertheless, now I remember Deri told me he hardcoded a lot of stuff
>>> for 1.22.4 which should be removed after the release of 1.23.0, so it
>>> seems that the time has come to chop a lot of stuff from there.
>>>
>>> Deri, would you mind simplifying the scripts assuming a Build-dep of
>>> groff(>=1.23.0)?
> 
> Resent the patch cc Deri.
> 
> Would it make sense to merge changes into/from groff 1.23 grodpf, which I also 
> tried, and also did not produce page footers, but did produce lots of 
> *different* messages.
> It seems likely that changes made to build the huge man book might also benefit 
> other projects with large docs.

We don't have a gropdf(1) copy anymore.  :)

> 
>>>> Are there any other scripts which need to be run and/or groff commands or data
>>>> which need to be supplied?
> 
>>> No.  It's just:
>>>
>>> $ cd scripts/LinuxManBook/
>>> $ ./BuildLinuxMan.pl ../../
> 
>>>> It would be nice to see this eventually added to your RELEASE doc, and maybe
>>>> also to the make scripts.
> 
>>> Yes.  I first want to put it in the Makefiles, and then add it to
>>> INSTALL.  Then something to RELEASE.  But I first want to simplify
>>> the script so I can understand it.
> 
> See below ;^>

Sooo true.

Cheers,
Alex

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-08-12  0:03 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07  1:16 [PATCH] scripts/LinuxManBook/gropdf: use symlink instead of hard coded groff version Brian Inglis
2023-08-07  2:46 ` No 6.05/.01 pdf book available Brian Inglis
2023-08-07  8:45   ` Alejandro Colomar
2023-08-07  9:16     ` Alejandro Colomar
2023-08-07 16:21       ` Brian Inglis
2023-08-12  0:02         ` Alejandro Colomar [this message]
2023-08-12  1:48           ` G. Branden Robinson
2023-08-12 21:32             ` Alejandro Colomar
     [not found]     ` <21975186.EfDdHjke4D@pip>
2023-08-11 23:51       ` Alejandro Colomar
2023-08-12  3:04         ` G. Branden Robinson
2023-08-12 21:33           ` Alejandro Colomar
2023-08-12 17:02       ` Brian Inglis
2023-08-12 20:02         ` Deri
2023-08-13 20:30           ` Brian Inglis
2023-08-13 20:47             ` Alejandro Colomar
2023-08-13 21:55               ` G. Branden Robinson
2023-08-13 22:45                 ` Alejandro Colomar
2023-08-13 22:18               ` Alejandro Colomar
2023-08-14  6:49                 ` Brian Inglis
2023-08-14 10:46                   ` Alejandro Colomar
2023-08-13 21:47             ` hyphens at ends of pages (was: No 6.05/.01 pdf book available) G. Branden Robinson
2023-08-14  5:28               ` Brian Inglis
2023-08-14 16:06             ` No 6.05/.01 pdf book available Deri
2023-08-14 17:37               ` Alejandro Colomar
2023-08-14 20:01                 ` Alejandro Colomar
2023-08-14 21:22                   ` Deri
2023-08-14 21:32                     ` Alejandro Colomar
2023-08-14 23:26                       ` Deri
2023-08-14 21:40                 ` Deri
2023-08-15  0:50                   ` groff features for hyperlinked man pages (was: No 6.05/.01 pdf book available) G. Branden Robinson
2023-08-15 10:34                     ` G. Branden Robinson
2023-08-18 13:50                     ` Alejandro Colomar
2023-08-19  4:37                       ` G. Branden Robinson
2023-10-01 12:02                         ` Alejandro Colomar
2023-08-18 10:29                   ` No 6.05/.01 pdf book available Alejandro Colomar
2023-08-15  0:34               ` Brian Inglis
2023-08-20 16:48                 ` Deri
2023-08-20 18:54                   ` Alejandro Colomar
2023-08-20 19:06                   ` Brian Inglis
     [not found]                     ` <3262525.44csPzL39Z@pip>
2023-08-21 22:02                       ` Alejandro Colomar
2023-08-21 23:10                         ` Deri
2023-08-21 23:45                         ` Brian Inglis
2023-08-28 12:17                           ` Alejandro Colomar
2023-08-28 18:24                             ` Brian Inglis
2023-08-28 21:11                               ` Alejandro Colomar
2023-08-07  8:29 ` [PATCH] scripts/LinuxManBook/gropdf: use symlink instead of hard coded groff version Alejandro Colomar
2023-08-07 15:01 ` Brian Inglis
2023-08-11 23:57 ` Alejandro Colomar

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=ac4a6675-f96a-cf39-f2c9-381d6ce0733b@kernel.org \
    --to=alx@kernel.org \
    --cc=Brian.Inglis@Shaw.ca \
    --cc=deri@chuzzlewit.myzen.co.uk \
    --cc=linux-man@vger.kernel.org \
    /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 NNTP newsgroup(s).