Daiki Ueno writes:
> I'm still not very happy with the name AM_GNU_GETTEXT_PREREQ and having
> a separate macro in the first place, but I couldn't think of any better
> way to implement the functionality without breaking compatibility.
I've merged this after renaming it to AM_GNU_GETTEXT_REQUIRE
Daiki Ueno writes:
> Roumen Petrov writes:
[...]
>> If understand idea is new archive to contain only "recent" versions.
>> Lets version 0.20.* not not add "drastic" change. Lest first "drastic"
>> version is 0.21.
>> Would you like to distribute archive with following content:
>> a) at relea
Roumen Petrov writes:
Hello Roumen,
Thanks for the comment.
> Why not first xxx_PREREQ, like AC_PREREQ . Then macro AM_GNU_GETTEXT
> could extract if version is requested.
> Otherwise PREREQ is ambiguous.
Good point. PREREQ would definitely need to check something at
M4 time, unlike AM_GNU_GE
Hello Daiki,
Daiki Ueno wrote:
Hello,
This is not for the imminent release, but I would like to hear opinions
on it.
In order to integrate gettext into autotools projects, we suggest
invoking AM_GNU_GETTEXT and AM_GNU_GETTEXT_VERSION, like this:
AM_GNU_GETTEXT([external])
AM_GNU_GETTEXT
Hello,
This is not for the imminent release, but I would like to hear opinions
on it.
In order to integrate gettext into autotools projects, we suggest
invoking AM_GNU_GETTEXT and AM_GNU_GETTEXT_VERSION, like this:
AM_GNU_GETTEXT([external])
AM_GNU_GETTEXT_VERSION([0.19.4])
This instructs a
