Re: [PATCH] do not refresh ratpoison.man.1 with --disable-maintainer-mode

"Bernhard R. Link" <[email protected]> writes:

> * Jérémie Courrèges-Anglas <[email protected]> [140325 11:40]:
>> 2. you received a tarball, you want to patch the mdoc(7) manpage, but
>>    you want to install the man(7) manpage (really?).
>>    -> Just patch the already shipped man(7) manpage.
>
> If you do that (without --disable-maintainer-mode), then you must make sure
> that you first patch the mdoc manpage and then the other one.
> Of if you patch both at the same time you need to do a manual touch of
> the one and then of the other (and if you want to do that portably with
> all file systems, you need some sleep in between).

Really, there's no reason to patch both manpages.  "Doctor, it hurts
when I press here." "Well, stop pressing."

> That's exactly what --disable-maintainer-mode is good for, so that you
> are able to do patching like that without running into that problems.

I think you've just emptied the set of advantages I thought
maintainer-mode could have.  Thanks. :)

>> I might use AM_MISSING_PROG though, to deal with those cases:
>> 
>>   tmp=`mktemp` &&   -Tman < ./ratpoison.mdoc.1 > "$tmp" &&  chmod 0644 "$tmp" &&  mv "$tmp" ./ratpoison.man.1
>>   /bin/sh: -Tman: not found
>> 
>> isn't exactly helpful.
>
> Fixing that is of course also nice, but that is an independent problem.
>
> Though I wonder is there a system without mdoc support? I'm suprised
> enough that there is a system without groff, but one without groff and
> still no mdoc support?

Some Solaris versions, which I suspect ratpoison can run on.  It's not
that I care much about them but thanks to mandoc(1) generating a man(7)
manpage for them is cheap.

-- 
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF  DDCC 0DFA 74AE 1524 E7EE

_______________________________________________
Ratpoison-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/ratpoison-devel