From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] package/wget: use the new gettextize infra
Date: Thu, 10 Apr 2014 07:12:06 +0200 [thread overview]
Message-ID: <20140410051206.GA3191@free.fr> (raw)
In-Reply-To: <20140410033422.GR4096@tarshish>
Baruch, All,
On 2014-04-10 06:34 +0300, Baruch Siach spake thusly:
> On Thu, Apr 10, 2014 at 12:20:05AM +0200, Yann E. MORIN wrote:
> > From: "Yann E. MORIN" <yann.morin.1998@free.fr>
> >
> > Currently, the gettextization of wget works by chance:
> > - host-gettext is added as a dependency to wget;
> > - gettextize is run as a post-patch hook.
> >
> > But the dependencies are only guaranteed to be built and installed
> > for the configure step, not the patch step. Becasue post-patch hooks
> > are part of the patch step, we have no guarantee that the dependency
> > to host-gettext is done by the time we gettextize wget.
> >
> > This happens to work by chance, since wget sorts alphabetically after
> > gettext, so we indeed have host-gettext built and installed by the
> > time we need to gettextize wget.
> >
> > This is prone to fail in the parallel build case, sicne we can no
> > longer rely on alphabetical order in that case.
>
> Fixing this only requires using PRE_CONFIGURE_HOOK instead of POST_PATCH_HOOK,
> isn't it? Is there anything else this series attempts to fix?
Yes, switching it to a pre-configure hook would fix it.
But that would be a one-off solution.
Providing it in the autotools-infra will allow us to have consistency
across packages and would allow us to fix it in a single place in the
future, rather than having to hunt down allow the offenders.
But as I said, this is an RFC, so we can discuss it further.
First, we have to agree we want it in the autotools infra or not.
Then, we'll have to check whether a boolean + an _OPT is enough, or if
we need something a bit more involved (e.g. let packages define the
complete hook, and just have the infra call it at the proper moment.)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-04-10 5:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 22:20 [Buildroot] [PATCH 0/3] [RFC] pkg-autotools: introduce infra to gettextize packages (branch yem/gettextize) Yann E. MORIN
2014-04-09 22:20 ` [Buildroot] [PATCH 1/3] pkg-autotools: add support to gettextize a package Yann E. MORIN
2014-04-09 22:20 ` [Buildroot] [PATCH 2/3] manual: add gettextize explanations in the manual Yann E. MORIN
2014-04-10 8:34 ` Thomas De Schampheleire
2014-04-09 22:20 ` [Buildroot] [PATCH 3/3] package/wget: use the new gettextize infra Yann E. MORIN
2014-04-10 3:34 ` Baruch Siach
2014-04-10 5:12 ` Yann E. MORIN [this message]
2014-04-10 21:19 ` [Buildroot] [PATCH 0/3] [RFC] pkg-autotools: introduce infra to gettextize packages (branch yem/gettextize) 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=20140410051206.GA3191@free.fr \
--to=yann.morin.1998@free.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.