Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/11 v3] Rework the gettext handling
Date: Thu, 20 Sep 2012 20:47:30 +0200	[thread overview]
Message-ID: <20120920204730.75b79901@skate> (raw)
In-Reply-To: <201209201850.56066.yann.morin.1998@free.fr>

Dear Yann E. MORIN,

On Thu, 20 Sep 2012 18:50:55 +0200, Yann E. MORIN wrote:

> My goal with the series was not to fix anything (except for the required
> fixes), but rather to improve on the existing infrastructure.

Agreed.

> Fixing anything that would break after the series, and that was already
> broken before the series, was not the goal. This can come in a later
> series [0], if such fixes are needed.
> 
> [0] Admitedly, it could (should?) even come before the series, but fixing
>     packages is really different from improving the infrastructure.
> 
> That being said, we now have a few venues to deal with this series:
>   0- drop the series entirely,
>   1- postpone this series until after all packages have been fixed,
>   2- finalise the series so it is fully agreed-on, apply it, then fix
>      packages,
>   3- get a benevolent dictator to agree the whole series for good,
>      apply it, then we can fix the packages,
>   4- apply all agreed-on patches (eg. 1-4, 6), then fix all packages,
>      then refine/drop currently not agreed-on patches.
>   5- apply all agreed-on patches (eg. 1-4, 6), then refine/drop the
>      rest of the series, apply it, and fix packages,
> 
> Hopefully, we all agree that 0 is out-of-question. ;-)
> 
> Although 1 would be the best technical solution, it is (IMHO) not the
> best from a practical point of view.
> 
> Going with 2 means another long round-trip, as there is at least one
> opposition to this series (although I hope Thomas can be coerced into
> approving the series! ;-p ).
> 
> 3 is not the best course of action, we still have not reached consensus
> on the technical (de)merits of the series (specifically the end of it).
> 
> I do not have a strong feeling between 4 and 5, although, from a personal
> position, I'd say we should go for 5, so I can get rid of this series
> entirely (and switch to other interesting stuff! ;-) ).

Peter, can you please apply now patches 1 to 8 in this series, so the
volume of the series reduces and we can more easily work on an
agreement for the remaining patches?

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-09-20 18:47 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-16 22:57 [Buildroot] [PATCH 0/11 v3] Rework the gettext handling Yann E. MORIN
2012-09-16 22:57 ` [Buildroot] [PATCH 01/11] gettext: remove option to build statically Yann E. MORIN
2012-09-16 22:57 ` [Buildroot] [PATCH 02/11] gettext: remove the gettext-target make target, unused Yann E. MORIN
2012-09-16 22:57 ` [Buildroot] [PATCH 03/11] gettext: remove libintl handling Yann E. MORIN
2012-09-16 22:57 ` [Buildroot] [PATCH 04/11] Remove all references to libintl Yann E. MORIN
2012-09-16 22:57 ` [Buildroot] [PATCH 05/11] gettext: convert to autotools-package Yann E. MORIN
2012-09-20 19:44   ` Arnout Vandecappelle
2012-09-20 19:46     ` Arnout Vandecappelle
2012-09-21  6:33       ` Peter Korsgaard
2012-09-16 22:57 ` [Buildroot] [PATCH 06/11] doc: update after gettext changes Yann E. MORIN
2012-09-16 22:57 ` [Buildroot] [PATCH 07/11] package/lshw: add missing dependency on gettext Yann E. MORIN
2012-09-16 22:57 ` [Buildroot] [PATCH 08/11] package/pulseaudio: fix build-dependency " Yann E. MORIN
2012-09-18 17:58   ` Thomas Petazzoni
2012-09-18 20:45     ` Yann E. MORIN
2012-09-16 22:57 ` [Buildroot] [PATCH 09/11] toolchain/common: rename BR2_NEEDS_GETTEXT Yann E. MORIN
2012-09-20 22:21   ` Arnout Vandecappelle
2012-09-21  5:10     ` Thomas Petazzoni
2012-09-16 22:57 ` [Buildroot] [PATCH 10/11] toolchain/common: introduce blind options BR2_NEEDS_GETTEXT{, _IF_LOCALE} Yann E. MORIN
2012-09-18 17:55   ` Thomas Petazzoni
2012-09-18 21:16     ` Samuel Martin
2012-09-18 21:28     ` Yann E. MORIN
2012-09-20 18:53       ` Thomas Petazzoni
2012-09-20 22:29       ` Arnout Vandecappelle
2012-09-20 22:24   ` Arnout Vandecappelle
2012-09-21  5:13     ` Thomas Petazzoni
2012-09-16 22:57 ` [Buildroot] [PATCH 11/11] packages: use the new gettext mechanism Yann E. MORIN
2012-09-18 21:17 ` [Buildroot] [PATCH 0/11 v3] Rework the gettext handling Samuel Martin
2012-09-19 21:11 ` Arnout Vandecappelle
2012-09-19 22:53 ` Arnout Vandecappelle
2012-09-20 16:50   ` Yann E. MORIN
2012-09-20 18:47     ` Thomas Petazzoni [this message]
2012-09-20 18:49 ` Thomas Petazzoni
2012-09-20 19:42 ` Peter Korsgaard

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=20120920204730.75b79901@skate \
    --to=thomas.petazzoni@free-electrons.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