Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] targets: move target options to their own sub-menu
Date: Fri, 16 Aug 2013 19:59:07 +0200	[thread overview]
Message-ID: <20130816175906.GA3422@free.fr> (raw)
In-Reply-To: <CAAXf6LVX6TR+dPhS_FGHZpf+-_j_XBaCVaQxFY+MFp=O7m+LNA@mail.gmail.com>

Thomas, All,

On 2013-08-16 12:30 +0200, Thomas De Schampheleire spake thusly:
> On Fri, Aug 16, 2013 at 12:24 PM, Thomas De Schampheleire
> <patrickdepinguin+buildroot@gmail.com> wrote:
> > On Fri, Aug 16, 2013 at 8:39 AM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> >> Thomas, Arnout, All,
> >>
> >> On Friday 16 August 2013 08:30:43 Thomas De Schampheleire wrote:
> >>> On Fri, Aug 16, 2013 at 1:10 AM, Arnout Vandecappelle <arnout@mind.be> wrote:
> >>> > On 15/08/13 22:28, Yann E. MORIN wrote:
> >>> >>
> >> I would even put the kernel before the packages, and bootloaders before
> >> kernel. Ie. I'd use the boot-time order of things:
> >>     (Target options)
> >>     Build options
> >>     Toolchain
> >>     System configuration
> >>     Bootloaders
> >>     Kernel
> >>     Packages selection
> >>     Filesystem images
> >>     Host Utilities
> >>     Legacy config options
> >>
> >> Bizzarely enough, moving bootloaders before kernel seems odd... :-/
> >
> >
> > I can follow this boot-time order strategy, but I concur with the
> > bootloader oddity.
> 
> [sorry, accidentally hit send button]
> 
> Here is a slightly different viewpoint: some users will never touch
> the bootloader. However, creating a kernel and rootfs (possibly
> attached to the kernel) is very common. This can result in the
> following order:
> 
> (Target options)
> Build options
> Toolchain
> System configuration
> Kernel
> Package selection for the target
> Filesystem images
> Bootloaders
> Host Utilities
> Legacy config options

Hey! It looks good to me! :-)
I'll handle this. Thanks!

> By the way: isn't it more logical to put 'Bootloaders' in singular
> (Bootloader), since one typically builds only one bootloader, just as
> one only builds one kernel...

This is two-sided:
  - either you consider what Buildroot has to offer: one kernel, and
    multiple bootloaders;
  - or you consider what the user may want to install on the targe, at
    most one kernel, and at most one bootloader.

I prefer the first option. If at some point in the future Buildroot gets
support for alternative kernels (GNU/Hurd, someone? ;-) ), then we'd
have to s/Kernel/Kernels/.

Consequently, "Package selection for the target" should be a plural
"Packages selection for target".

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:[~2013-08-16 17:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-15 20:28 [Buildroot] [PATCH] targets: move target options to their own sub-menu Yann E. MORIN
2013-08-15 23:10 ` Arnout Vandecappelle
2013-08-16  6:30   ` Thomas De Schampheleire
2013-08-16  6:39     ` Yann E. MORIN
2013-08-16 10:24       ` Thomas De Schampheleire
2013-08-16 10:30         ` Thomas De Schampheleire
2013-08-16 17:59           ` Yann E. MORIN [this message]
2013-08-16 19:04             ` Thomas De Schampheleire
2013-08-18 16:41             ` Thomas Petazzoni
2013-08-19 16:33       ` Arnout Vandecappelle
2013-08-18  7:24 ` Thomas De Schampheleire

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=20130816175906.GA3422@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox