From: "Dmitry V. Levin" <ldv@altlinux.org>
To: Mark Wielaard <mark@klomp.org>
Cc: elfutils-devel@sourceware.org
Subject: Re: [PATCH] Modernize gettext infrastructure
Date: Wed, 16 Dec 2020 17:59:48 +0300 [thread overview]
Message-ID: <20201216145945.GB30159@altlinux.org> (raw)
In-Reply-To: <6aab7f98c38ac2eef357622f8a2073c0ac855a2c.camel@klomp.org>
Hi Mark,
On Wed, Dec 16, 2020 at 03:05:54PM +0100, Mark Wielaard wrote:
> Hi Dmitry,
>
> On Wed, 2020-12-16 at 02:40 +0300, Dmitry V. Levin wrote:
> > Switch to use AM_GNU_GETTEXT, AM_GNU_GETTEXT_VERSION, and
> > AM_GNU_GETTEXT_REQUIRE_VERSION, this allows to stop bundling gettext
> > infrastructure files and let autoreconf invoke autopoint which will
> > set the gettext infrastructure up.
>
> This is a good idea. And as far as I can see this is correct.
>
> But it does mean for a git checkout people now need to have gettext-
> tools installed (but not for a released build).
I suppose people are used to it nowadays, given that AM_GNU_GETTEXT
and AM_GNU_GETTEXT_VERSION are quite widespread macros.
> I don't know if all the
> buildbot workers have it installed, so when you do check it in please
> keep an eye on
> https://builder.wildebeest.org/buildbot/#/builders?tags=elfutils
Is there a way to find it out beforehand?
--
ldv
next prev parent reply other threads:[~2020-12-16 14:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 23:40 Dmitry V. Levin
2020-12-15 23:46 ` Q: splitting the top level .gitignore file Dmitry V. Levin
2020-12-16 13:44 ` Mark Wielaard
2020-12-20 12:11 ` [PATCH 1/2] Split " Dmitry V. Levin
2020-12-20 15:28 ` Mark Wielaard
2020-12-20 15:37 ` Dmitry V. Levin
2020-12-20 15:59 ` Dmitry V. Levin
2020-12-20 16:09 ` Mark Wielaard
2020-12-20 12:11 ` [PATCH 2/2] Update .gitignore files Dmitry V. Levin
2020-12-16 14:05 ` [PATCH] Modernize gettext infrastructure Mark Wielaard
2020-12-16 14:59 ` Dmitry V. Levin [this message]
2020-12-16 15:10 ` Mark Wielaard
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=20201216145945.GB30159@altlinux.org \
--to=ldv@altlinux.org \
--cc=elfutils-devel@sourceware.org \
--cc=mark@klomp.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 read-only IMAP folder(s) and NNTP newsgroup(s).