All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2] Fix pkg-kconfig infra (branch yem/kconfig)
Date: Mon, 4 Aug 2014 21:58:07 +0200	[thread overview]
Message-ID: <20140804195807.GC3875@free.fr> (raw)
In-Reply-To: <e6001c6d-be6d-4d79-8136-88979fc1ea29@email.android.com>

Thomas, All,

On 2014-08-04 20:13 +0200, Thomas De Schampheleire spake thusly:
> "Yann E. MORIN" <yann.morin.1998@free.fr> schreef:
> >Hello All!
> >
> >This series fixes a nasty regression introduced with the pkg-kconfig
> >infrastructure recently applied, whereby kconfig packages are always
> >rebuilt on each 'make'.
> >
> >The proposed fix consists in a post-configure hook, and I believe this
> >is enough to get us rolling for the next release.
> >
> >A better fix would be to move the call to 'oldocnifg' out of the
> >packages, and into the kconfig infra itself, but this is a bit more
> >involved. This could be done in -next (or maybe in master shortly after
> >-rc1 if possible).
> 
> For uclibc, the oldconfig call is actually part of the fixup commands,
> so no problem there, right?

Right, I did look at it, and it should work OK.

> What if we do the same for busybox?

Well, I do not know what your plans are for the other kconfig packages,
so I came up with the hook solution, because it is fool-proof against
any future kconfig package messing arounf with oldconfig, and because we
need a quick fix.

But as I said in the cover-letter, we can further improve the situation
in -next.

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.  |
'------------------------------^-------^------------------^--------------------'

      reply	other threads:[~2014-08-04 19:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-04 17:20 [Buildroot] [PATCH 0/2] Fix pkg-kconfig infra (branch yem/kconfig) Yann E. MORIN
2014-08-04 17:20 ` [Buildroot] [PATCH 1/2] infra/pkg-kconfig: join comments to the related code-block Yann E. MORIN
2014-08-04 17:24   ` Thomas De Schampheleire
2014-08-04 17:28     ` Yann E. MORIN
2014-08-04 17:24 ` [Buildroot] [PATCH 2/2] infra/pkg-kconfig: do not rebuild kconfig packages again and again Yann E. MORIN
2014-08-04 17:32   ` Thomas De Schampheleire
2014-08-04 17:36     ` Thomas De Schampheleire
2014-08-04 17:37     ` Yann E. MORIN
2014-08-04 18:13 ` [Buildroot] [PATCH 0/2] Fix pkg-kconfig infra (branch yem/kconfig) Thomas De Schampheleire
2014-08-04 19:58   ` Yann E. MORIN [this message]

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=20140804195807.GC3875@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.