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] Makefile: check rootfs overlays with BR2_ROOTFS_MERGED_USR enabled
Date: Sat, 5 May 2018 16:45:27 +0200	[thread overview]
Message-ID: <20180505144527.GA14524@scaer> (raw)
In-Reply-To: <898911315.1288101.1525528062390.JavaMail.zimbra@datacom.ind.br>

Carlos, All,

On 2018-05-05 10:47 -0300, Carlos Santos spake thusly:
> > From: "Yann E. MORIN" <yann.morin.1998@free.fr>
> > To: "Carlos Santos" <casantos@datacom.ind.br>
> > Cc: "buildroot" <buildroot@buildroot.org>
> > Sent: Saturday, May 5, 2018 7:01:00 AM
> > Subject: Re: [Buildroot] [PATCH] Makefile: check rootfs overlays with BR2_ROOTFS_MERGED_USR enabled
> 
> > Carlos, All,
> > 
> > On 2018-05-03 09:19 -0300, Carlos Santos spake thusly:
> >> Since commit 0db34529f48 we use rsync with the --keep-dirlinks option to
> >> prevent overlays from accidentally overwriding /{usr,bin,sbin,lib} links
> >> when BR2_ROOTFS_MERGED_USR option is enabled. Unfortunately this also
> >> prevents replacing a symlink by a directory on purpose (e.g. /var/log,
> >> to persist system logs).
> > 
> > In that case, I suggest your use a post-build script instead.
> 
> That was my first approach.
> 
> > In facct, I think that any modifications that change the layout of the
> > filesystem should be done as a post-build script rather than an overlay.
> > 
> > So, I am pretty much reluctant to see this patch go in.
> 
> This change does not prevent the user from using a post-build but I'd
> prefer to let Buildroot check the correctness of user changes as much
> as possible instead of just prohibiting them.

It's not about prohibiting them.

But I'd prefer we keep things simple in Buildroot, and since there is
already a way to do it, I don't mind that overlays do not provide this
solution. A post-build script is way more versatile when it comes to
changing the layout.

> Overlays are simpler to create and less error prone than scripts. They
> are also self-documented, since a "find" or "tree" command shows the
> resulting structure.

True, but they are less versatile...

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:[~2018-05-05 14:45 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 [this message]
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
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=20180505144527.GA14524@scaer \
    --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