From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: "José Pekkarinen" <jose.pekkarinen@unikie.com>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] system: add optional rsync with preserved permissions
Date: Mon, 4 Oct 2021 09:00:36 +0200 [thread overview]
Message-ID: <20211004090036.65722dda@windsurf> (raw)
In-Reply-To: <20211004064143.6281-1-jose.pekkarinen@unikie.com>
Hello,
On Mon, 4 Oct 2021 09:41:43 +0300
José Pekkarinen <jose.pekkarinen@unikie.com> wrote:
> +config BR2_ROOTFS_OVERLAY_PRESERVED_PERMISSION
> + string "Preserve permissions of overlay directories"
> + depends on BR2_ROOTFS_OVERLAY
> + default "n"
> + help
> + Preserve file permissions of specified overlay.
I'm afraid we probably won't want an option like this.
The question is why in the existing SYSTEM_RSYNC we don't preserve
permissions? I can imagine because sometimes they can be wrong in the
original overlay, for example with version control systems that put all
files read-only.
Yann, Arnout: do you remember why SYSTEM_RSYNC has --chmod=u=rwX,go=rX ?
José: have you considered using a permission table to fixup the
permissions ?
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-10-04 7:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 6:41 [Buildroot] [PATCH] system: add optional rsync with preserved permissions José Pekkarinen
2021-10-04 7:00 ` Thomas Petazzoni [this message]
2021-10-04 7:08 ` José Pekkarinen
2021-10-04 7:30 ` Thomas Petazzoni
2021-10-04 15:15 ` Yann E. MORIN
2021-10-04 15:10 ` Yann E. MORIN
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=20211004090036.65722dda@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=jose.pekkarinen@unikie.com \
--cc=yann.morin.1998@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.