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] Buildroot Developer Day, Friday 3rd February, Brussels
Date: Fri, 27 Jan 2012 12:58:05 +0100	[thread overview]
Message-ID: <20120127125805.580febd8@skate> (raw)
In-Reply-To: <201201271133.20517.arnout@mind.be>

Hello,

Le Fri, 27 Jan 2012 11:33:20 +0100,
Arnout Vandecappelle <arnout@mind.be> a ?crit :

>  I have a list of 21 ideas for things that I'd like to change in
> buildroot. Any interest in me going over that list?  The most
> important ones are:
> 
>  -- support for overlays (cfr. openembedded)

Ok. I am not sure how it is possible without making Buildroot way more
complicated, but we can have a look at this.

>  -- support for image-in-image (e.g. cpio+kernel on an ext3+grub on
> an MBR partition)

Ok.

> -- shared infrastructure for xxx-yyyconfig

Not sure what you mean here?

>  -- shared infrastructure for non-autotools builds

We already have GENTARGETS, what else do you want? Of course, we can
create infrastructure for Python modules or other types of build
systems, but I'm not sure this is what you're referring to.

>  Also we should make a decision on the host-tools menu that was
> posted on the list before.

Peter has said he was OK with this during the Prague meeting, so I
think the decision has been taken. It only needs to be applied :-)

Peter: could you try to handle the patches in a more FIFO fashion,
rather than the LIFO fashion you're using these days? There are many
patches that have been waiting for a very long time, while the most
recent patches are being taken into account very quickly. Some
examples: the host tools menu Arnout is referring to, or Maxime
Ripard's patches on the per-package device/permission stuff.

Best regards,

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-01-27 11:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-23 23:08 [Buildroot] Buildroot Developer Day, Friday 3rd February, Brussels Thomas Petazzoni
2012-01-24  9:56 ` Thomas Petazzoni
2012-01-25 11:03 ` Thomas De Schampheleire
2012-01-25 12:57   ` Thomas Petazzoni
2012-01-25 18:04     ` Michael S. Zick
2012-01-25 18:07       ` Michael S. Zick
2012-01-27 10:33   ` Arnout Vandecappelle
2012-01-27 11:58     ` Thomas Petazzoni [this message]
2012-01-27 15:24       ` Peter Korsgaard
2012-01-27 15:27         ` Thomas Petazzoni
2012-01-27 15:32           ` Yegor Yefremov
2012-01-27 15:36             ` Thomas Petazzoni
2012-01-27 15:50               ` Yegor Yefremov
2012-01-27 15:52                 ` Thomas Petazzoni
2012-01-27 19:36                   ` Peter Korsgaard
2012-01-30  9:19     ` Thomas De Schampheleire
2012-01-30  9:42       ` Peter Korsgaard
2012-01-30 14:16         ` Thomas De Schampheleire
2012-01-30 15:09           ` Peter Korsgaard
2012-01-30 11:26       ` Thomas Petazzoni
2012-01-29 15:46   ` Luca Ceresoli

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=20120127125805.580febd8@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