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 of 7] Introduction of kconfig-package infrastructure
Date: Tue, 29 Jul 2014 23:52:08 +0200	[thread overview]
Message-ID: <20140729235208.674744cc@free-electrons.com> (raw)
In-Reply-To: <patchbomb.1406224167@localhost>

Dear Thomas De Schampheleire,

On Thu, 24 Jul 2014 19:49:27 +0200, Thomas De Schampheleire wrote:

> This patch series introduces a kconfig-package infrastructure and already
> converts the uclibc and busybox packages.
> The series is based on the to-be-applied uclibc patch series that improves the
> behavior of the kconfig parts.

Weird, you don't have the summary of patches in the cover letter. Don't
you use 'git --cover format-patch' to generate the cover letter?

Anyway:

 * I've applied two preparation patches of this series:
   uclibc: use $(MAKE) iso $(MAKE1) for menuconfig target
   linux: remove support of linux26-* targets

   This way, you don't have to carry them anymore.

 * Regarding the kconfig-package infra stuff, I'm mostly fine with it,
   except for one detail: it pretends to be a package infrastructure,
   but it is not. It is only a kind of "library" / "helper" to use next
   to a real package infrastructure. And I think this is pretty
   confusing considering the name that was chosen, and the way it works.

   My proposal would therefore be to turn it into a real package
   infrastructure by simply making it inherit from generic-package,
   much like autotools-package, cmake-package and al. All kconfig-based
   packages are otherwise generic-package. I don't see the logic behind
   using Kconfig for an autotools-based or cmake-based package, since
   autotools and cmake are precisely here to provide configuration
   capabilities that overlap with what kconfig provides. And as of
   today, we have linux, barebox, uclibc and busybox, and all of these
   use the generic-package infra.

   I think it's really a minor change in the patches, and with this
   change, I'm willing to merge this package infra.

Of course, comments/reviews from others are more than welcome!

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2014-07-29 21:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24 17:49 [Buildroot] [PATCH 0 of 7] Introduction of kconfig-package infrastructure Thomas De Schampheleire
2014-07-24 17:49 ` [Buildroot] [PATCH 1 of 7] infra: introduce a " Thomas De Schampheleire
2014-07-24 17:49 ` [Buildroot] [PATCH 2 of 7] uclibc: use $(MAKE) iso $(MAKE1) for menuconfig target Thomas De Schampheleire
2014-07-24 17:49 ` [Buildroot] [PATCH 3 of 7] uclibc: convert to kconfig-package infrastructure Thomas De Schampheleire
2014-07-24 17:49 ` [Buildroot] [PATCH 4 of 7] uclibc: only add kconfig targets if uclibc is enabled Thomas De Schampheleire
2014-07-24 17:49 ` [Buildroot] [PATCH 5 of 7] busybox: convert to kconfig-package infrastructure Thomas De Schampheleire
2014-07-24 17:49 ` [Buildroot] [PATCH 6 of 7] busybox: only add kconfig targets if uclibc is enabled Thomas De Schampheleire
2014-07-24 17:49 ` [Buildroot] [PATCH 7 of 7] linux: remove support of linux26-* targets Thomas De Schampheleire
2014-07-29 21:52 ` Thomas Petazzoni [this message]
2014-07-30 17:58   ` [Buildroot] [PATCH 0 of 7] Introduction of kconfig-package infrastructure Thomas De Schampheleire
2014-07-30 19:23     ` Thomas Petazzoni
2014-07-30 20:01       ` Thomas De Schampheleire
2014-07-31  6:57 ` Jeremy Rosen
2014-07-31  8:03   ` Thomas De Schampheleire
2014-07-31  8:20     ` Jeremy Rosen
2014-07-31 12:54       ` Matthew Weber

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=20140729235208.674744cc@free-electrons.com \
    --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