@Rene

Actually, coreutils builds happily without this patch, (I tried with it disabled,) is there a reason to leave it in anymore?

Personally I prefer not to have patches, (yeah I know they are a unfortunate necessity,) and tend to disable those not needed, can break things later, or irrelevant nowadays. Especially when overall system memory size is what it is nowadays. Now, back when 64k was considered a large system, well....

regards to both

-------- Forwarded Message --------
Subject: Re: [t2] new coreutils disable_man.patch.cross. hunk 1 was failing
Date: Sat, 12 Jan 2019 08:49:47 -0600
From: Joe Kozak <[email protected]>
To: scsijon <[email protected]>

no i dont know what im doing.


On Fri, Jan 11, 2019 at 8:01 PM scsijon <[email protected]> wrote:

The first hunk in the patch has changed with a couple of extra lines in
the local.mk before the lines to be changed

The second hunk can be removed as it's been fully implemented (and it's
moved a few lines anyway).

I just hadn't got to doccumenting it yet! Do you want to do it please Joe.

:-)

On 12/01/19 06:20, Joe Kozak wrote:
> --- coreutils-8.30/man/local.mk.vanilla 2019-01-11 19:10:51.548587784
+0000
> +++ coreutils-8.30/man/local.mk 2019-01-11 19:11:10.313691725 +0000
>
> @@ -23,11 +23,11 @@
>   run_help2man = $(SHELL) $(srcdir)/man/dummy-man
>   else
>   ## Graceful degradation for systems lacking perl.
> -if HAVE_PERL
> -run_help2man = $(PERL) -- $(srcdir)/man/help2man
> -else
> +#if HAVE_PERL
> +#run_help2man = $(PERL) -- $(srcdir)/man/help2man
> +#else
>   run_help2man = $(SHELL) $(srcdir)/man/dummy-man
> -endif
> +#endif
>   endif
>
>   man1_MANS = @man1_MANS@
>
>
> @@ -195,8 +195,8 @@
>    && export SOURCE_DATE_EPOCH && $(run_help2man) \
>         --source='$(PACKAGE_STRING)' \
>         --include=$(srcdir)/man/$$name.x \
> -      --output=$$t/$$name.1 \
>         --info-page='\(aq(coreutils) '$$name' invocation\(aq' \
> +      --output=$$t/$$name.1 \
>         $$t/$$argv$(EXEEXT) \
>      && sed \
>           -e 's|$*\.td/||g' \
>




----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2

Reply via email to