Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] Makefile: add media image generation
Date: Thu, 19 Mar 2015 23:46:19 +0100	[thread overview]
Message-ID: <550B51BB.1030703@mind.be> (raw)
In-Reply-To: <1651296559.1406375.1426797068089.JavaMail.zimbra@savoirfairelinux.com>

On 19/03/15 21:31, Vivien Didelot wrote:
> Hi Yann,
> 
> If I understand correctly, you are saying that genimage may not cover
> every use cases. And that is totally fine.
> 
> With this patchset, I didn't mean to implement in Buildroot the
> *ultimate* framework for media image generation, but simply provide an
> *optional* and convenient path to the user.

 I completely agree with this statement. And I think that was also the
conclusion from the genimages patch series: it's nice to have something that
allows you to generate an SD card image, but not at the cost of adding too much
complexity to buildroot.

 However...

[snip]
> If we want to add more tools in the future, this is very good. Similar
> to the actual "Init system" where you can choose between BusyBox,
> systemV, etc., you may want to use different composition tools for
> different projects.

 Here I disagree, I see no reason to support more than one image generation
system. It's not something that ends up on the target, it's just part of the
build process, so just an implementation detail. It would be like offering the
choice between fakeroot or fakeroot-ng...

 We _may_ choose to switch to a different media generation system in the future,
but that's a different story.


 Regards,
 Arnout

> 
> This might be prematurate for the moment, but we can imagine the
> following menu in the future:
> 
>     Media image generation  --->
>         [*] genimage
>         (board/raspberrypi/genimage.cfg) Path to genimage config files
>         [ ] genimages ;-)
>         [ ] wic
> 
> 
> We are using genimage for several projects and we didn't need much so
> far. Other people seem to share the same experience.
> 
> (*) genimage does have a "mountpoint" option for partitions btw, but I
> have not played with it yet.
> 
> Thanks,
> -v
[snip]


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2015-03-19 22:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17 22:51 [Buildroot] [PATCH 0/5] media image generation Vivien Didelot
2015-03-17 22:51 ` [Buildroot] [PATCH 1/5] Makefile: add " Vivien Didelot
2015-03-19  0:04   ` Yann E. MORIN
2015-03-19  8:27     ` Thomas Petazzoni
2015-03-19  8:44       ` Yann E. MORIN
2015-03-19  9:19         ` Thomas Petazzoni
2015-03-19 17:37           ` Vivien Didelot
2015-03-19 18:25             ` Yann E. MORIN
2015-03-19 20:31               ` Vivien Didelot
2015-03-19 22:46                 ` Arnout Vandecappelle [this message]
2015-03-19 22:05     ` Arnout Vandecappelle
2015-03-17 22:51 ` [Buildroot] [PATCH 2/5] board/raspberrypi: install Device Tree Vivien Didelot
2015-03-18 22:44   ` Yann E. MORIN
2015-03-18 23:05     ` Vivien Didelot
2015-03-17 22:51 ` [Buildroot] [PATCH 3/5] board/raspberrypi: add a genimage config Vivien Didelot
2015-03-17 22:51 ` [Buildroot] [PATCH 4/5] board/beaglebone: " Vivien Didelot
2015-03-17 22:51 ` [Buildroot] [PATCH 5/5] board/wandboard: " Vivien Didelot
2015-03-19 22:57 ` [Buildroot] [PATCH 0/5] media image generation Arnout Vandecappelle
2015-03-20  0:52   ` Vivien Didelot

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=550B51BB.1030703@mind.be \
    --to=arnout@mind.be \
    --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