[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: recursive install-pdf fails in po directory (was: Re: bison-2.5 rele

From: Akim Demaille
Subject: Re: recursive install-pdf fails in po directory (was: Re: bison-2.5 released [stable])
Date: Mon, 16 Apr 2012 11:18:31 +0200

Hi all,

I don't understand what is going on here.  This patch has been
sent already to bug-gettext and bug-gnulib, but each time it
seems to have caught no attention.  I agree this patch
addresses a very minor flaw, yet a genuine one.  These
targets are explicitly mandated by the GCS:

> @item install-html
> @itemx install-dvi
> @itemx install-pdf
> @itemx install-ps
> These targets install documentation in formats other than Info;
> they're intended to be called explicitly by the person installing the
> package, if that format is desired.  GNU prefers Info files, so these
> must be installed by the @code{install} target.

This issue affects *all* the projects that use Gettext, and the
fix is straightforward, so please, if something is wrong about
it, help me fix it.

FWIW, this patch, and a few others waiting for some feedback,
are holding the release of Bison 2.5.1.



Le 9 avr. 2012 à 10:15, Akim Demaille a écrit :

> Le 6 avr. 2012 à 14:46, Akim Demaille a écrit :
>> [sorry, I meant to Cc to bug-gnulib, but forgot to do so]
>> Hi Bruno, Hi gettexters!
>> I have not seen answers to this message.  Was something done in
>> gettext about this?  I see there is a gnulib/build-aux/po/Makefile.in.in
>> that exists, which is silently different from that of Gettext,
>> but which has the same problem.  Should the patch be sent to
>> gnulib instead?
> This is the said patch, prepared for gnulib instead of Gettext.
> I see no .PHONY in that file, so none was added.  What's the
> rationale?
> Thanks!
> <0001-Fix-recursion-of-install-into-po-directories.patch>

Attachment: 0001-Fix-recursion-of-install-into-po-directories.patch
Description: Binary data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]