Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Makefile: check rootfs overlays with BR2_ROOTFS_MERGED_USR enabled
Date: Sat, 05 May 2018 17:26:35 +0200	[thread overview]
Message-ID: <87d0yaunro.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180505150621.GB14524@scaer> (Yann E. MORIN's message of "Sat,  5 May 2018 17:06:21 +0200")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

Hi,

 >> Why? Overlays is the the recommended way to add/override stuff, and the
 >> 'everything-you-put-in-the-overlay-will-override-the-buildroot-defaults'
 >> is a pretty nice and easy to understand behaviour.

 > Well, I disagree quite a bit: overlays are ugly and 99% of what users
 > do with an overlay can be done with a package (i.e. adding data blobs).
 > The remaining 1% can be done with a post-build script.

 > Besides, what you put in an overlay is never accoutnted for: no
 > graph-size, no legal-info, no nothing...

 > Repeat after me: overlays are ugly! ;-)

 > Two things that overlays are noce for:

 >   - provide /etc/-style config files to be written over the default ones,

 >   - provide test-data that is not supposed to go into production, and
 >     for which a package may be a bit overkill, and even then...

 > Otherwise, overlays are just a pita and, long term, are a liability...

Do you feel better now? ;) I agree that they can be abused - But don't
forget, overlays were added to get people away from custom skeletons. I
still find overlays quite a bit nicer than custom skeletons.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2018-05-05 15:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-03 12:19 [Buildroot] [PATCH] Makefile: check rootfs overlays with BR2_ROOTFS_MERGED_USR enabled Carlos Santos
2018-05-05 10:01 ` Yann E. MORIN
2018-05-05 13:47   ` Carlos Santos
2018-05-05 14:45     ` Yann E. MORIN
2018-05-05 15:01       ` Peter Korsgaard
2018-05-05 15:21         ` Yann E. MORIN
2018-05-05 18:13           ` Arnout Vandecappelle
2018-05-05 14:41   ` Peter Korsgaard
2018-05-05 15:06     ` Yann E. MORIN
2018-05-05 15:26       ` Peter Korsgaard [this message]
2018-05-05 14:54 ` Peter Korsgaard

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=87d0yaunro.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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