Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/gettext-tiny: Add new package
Date: Tue, 21 Aug 2018 19:36:16 +0200	[thread overview]
Message-ID: <20180821193616.5634b4dc@windsurf> (raw)
In-Reply-To: <CAMw6YJ+FS=z0MQqWj3K-21QYR5m-20wE2RbfFHQnc1WdgrYwLA@mail.gmail.com>

Hello,

On Tue, 21 Aug 2018 18:51:00 +0300, Vadim Kochan wrote:

> I got the point, so it is not really useful to add gettext-tiny just as a
> package but integrate it
> as gettext alternative. So let me clarify - you expect to see this at least
> as series:
> 1) add package
> 2) integrate it as gettext alternative

Yes, exactly. And as Baruch suggested, it would be excellent if we
could also use host-gettext-tiny as an alternative to host-gettext.

This will raise a few questions:

 - There are a few packages that unconditionally need host-gettext. Is
   this really true ?

 - Some packages need host-gettext because of the AM_ICONV m4 macro
   provided by gettext.m4. Is gettext-tiny also providing the
   gettext-related m4 macros ?

Overall, I believe it's not an easy task and it may take some time, but
it is definitely worth the effort, and I'll be happy to support this
effort.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-08-21 17:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-21 14:22 [Buildroot] [PATCH 1/1] package/gettext-tiny: Add new package Vadim Kochan
2018-08-21 14:31 ` Baruch Siach
     [not found]   ` <CACV=4zeWfsgbrQx4g2cmssEjtwvPj+a_9Fu5FzfSH4h_Q4fXdw@mail.gmail.com>
2018-08-21 14:44     ` Baruch Siach
2018-08-21 15:29   ` Thomas Petazzoni
2018-08-21 15:51     ` Vadim Kochan
2018-08-21 17:36       ` Thomas Petazzoni [this message]
2018-08-21 20:07         ` Vadim Kochan
2018-08-21 20:10           ` Thomas Petazzoni
2018-08-22  7:02             ` Vadim Kochan
2018-10-09 12:45 ` Thomas Petazzoni
2018-10-09 13:12   ` Vadim Kochan
2018-10-09 13:12     ` Thomas Petazzoni

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=20180821193616.5634b4dc@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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