From: "Étienne Phélip" <etienne.phelip@savoirfairelinux.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC 4/4] board/acmesystems/aria-g25: set BR2_GENIMAGE_CFG_FILES
Date: Mon, 10 Apr 2017 09:44:32 -0400 (EDT) [thread overview]
Message-ID: <674007428.52191.1491831872252.JavaMail.zimbra@savoirfairelinux.com> (raw)
In-Reply-To: <20170405181424.1d69fee5@free-electrons.com>
Good morning everyone,
----- Le 5 Avr 17, ? 12:14, Thomas Petazzoni thomas.petazzoni at free-electrons.com a ?crit :
> Hello,
>
> On Wed, 5 Apr 2017 17:02:36 +0200, Arnout Vandecappelle wrote:
>
>> Combined with the other discussion in this thread, long-term I see us evolving
>> towards:
>>
>> - deprecate some of the finer-grain fs tuning options we have now;
>> - always using genimage to generate the target filesystems;
>> - position our fs targets more as a 'quick fix' solution than for production;
>> - make host-e2fsprogs etc. blind options again.
>
> To be honest, I am not sure I share this long-term view. I like the way
> things are done today, very modular: we can generate just a filesystem
> image, optionally use genimage afterwards, etc. So the "always using
> genimage to generate the target filesystem" is not something that I see
> as an improvement, for example.
To sum things up:
- Should I add BR2_GENIMAGE_CFG_FILES or reuse the script in the
postimage script
- if BR2_GENIMAGE_CFG_FILES is choosen, should it 'depends on' or
'select' BR2_PACKAGE_HOST_GENIMAGE?
- should I convert all boards or just the one already in this RFC?
Best regards
-Etienne
next prev parent reply other threads:[~2017-04-10 13:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 14:51 [Buildroot] [RFC 0/4] add genimage Kconfig entry Etienne Phelip
2017-03-29 14:51 ` [Buildroot] [RFC 1/4] support/scripts: add generic genimage script Etienne Phelip
2017-03-30 22:51 ` Arnout Vandecappelle
2017-04-01 13:50 ` Thomas Petazzoni
2017-03-29 14:51 ` [Buildroot] [RFC 2/4] system: add option to pass genimage config files Etienne Phelip
2017-03-29 14:51 ` [Buildroot] [RFC 3/4] configs/raspberrypi3_defconfig: set BR2_GENIMAGE_CFG_FILES Etienne Phelip
2017-03-29 14:51 ` [Buildroot] [RFC 4/4] board/acmesystems/aria-g25: " Etienne Phelip
2017-03-30 22:51 ` Arnout Vandecappelle
2017-03-31 7:46 ` Andreas Naumann
2017-03-31 16:34 ` Arnout Vandecappelle
2017-04-03 13:01 ` Andreas Naumann
2017-04-03 13:54 ` Arnout Vandecappelle
2017-04-05 6:38 ` Andreas Naumann
2017-04-05 12:38 ` Arnout Vandecappelle
2017-04-01 13:51 ` Thomas Petazzoni
2017-04-03 9:06 ` Peter Korsgaard
2017-04-03 9:35 ` Arnout Vandecappelle
2017-04-04 21:34 ` Peter Korsgaard
2017-04-05 15:02 ` Arnout Vandecappelle
2017-04-05 16:14 ` Thomas Petazzoni
2017-04-10 13:44 ` Étienne Phélip [this message]
2017-04-10 15:06 ` Arnout Vandecappelle
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=674007428.52191.1491831872252.JavaMail.zimbra@savoirfairelinux.com \
--to=etienne.phelip@savoirfairelinux.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