From: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 0/9] target permissions
Date: Mon, 24 Nov 2014 19:17:28 -0300 [thread overview]
Message-ID: <5473AE78.1000900@vanguardiasur.com.ar> (raw)
In-Reply-To: <1416586748-12936-1-git-send-email-guido@vanguardiasur.com.ar>
On 11/21/2014 01:18 PM, Guido Mart?nez wrote:
> Hey guys,
>
> fourth patchset to fix the target permissions variability.
>
> I checked (to the best of my knowledge) every 'cp' and 'rsync' call
> under package/. There are two bigs cases:
>
> (1) Copies from the package or download directory to the build directory
> (example: cache-calibrator, fan-ctrl, ramspeed, samba4). They are OK,
> since they copy source code, a Makefile or some other build files. These
> files _shouldn't_ affect the result, so I left them the way they are. We
> can change them if you agree, but I thought it'd be too much noise for
> now.
>
> (2) Copies from anything under output/ to the target. These should
> all be fine. Since we now build with a controlled umask and reset any
> permissions that could vary (tar files don't vary), we shouldn't observe
> any variability under output/ (modulo (1)-kind copies).
>
> I tested parallel builds with this, as Yann suggested, and they seem to
> work the same, which is expected since we just wrap everything at the
> top level.
>
> Differences from v3 are:
>
> - Recursive running of make is done with $(MAKE), and not using
> --no-print-directory. Also, change the "%" rule in "$(MAKECMDGOALS)"
> to properly detect phony rules.
>
> - Use --chmod on the external toolchain's rsync, to prevent any weird
> permissions coming from there. This isn't stricly necessary, since the
> toolchain libs are copied to the target via 'install', which won't
> depend on any existing permissions. But this way we're safer in case
> anything changes in the future. Also we make sure everything under
> output/ is controlled.
>
> - Fix some cp's to the target from non-controlled dirs
> on boot/grub/grub.mk, fs/iso9660/iso9660.mk, and
> board/boundarydevices/nitrogen6x/post-build.sh
>
> - Fifth patch dropped as it was accepted.
>
> - Added the umask setting in the Makefile generated in the $(O) dir.
> This is just an optimization so we don't have another level of 'make'
> running.
>
> - Fixed 'install' call on matchbox-keyboard patch (#4)
>
> Thanks!
>
> ---
>
> Guido Mart?nez (9):
> Makefile: don't depend on the umask
> Makefile: don't depend on current skeleton/overlay permissions
> toolchain/helpers.mk: use --chmod on rsync
> pkg-generic.mk: don't depend on external package permissions
> package: matchbox-keyboard: use install instead of cp
> scripts: mkmakefile: set umask before calling BR's makefile
> nitrogen6x: use install instead of cp
> boot/grub: use install instead of cp
> fs/iso9660: use install instead of cp
>
> Makefile | 19 +++++++++++++++++--
> board/boundarydevices/nitrogen6x/post-build.sh | 6 +++---
> boot/grub/grub.mk | 14 +++++++-------
> fs/iso9660/iso9660.mk | 16 +++++++++-------
> .../matchbox/matchbox-keyboard/matchbox-keyboard.mk | 2 +-
> package/pkg-generic.mk | 2 +-
> support/scripts/mkmakefile | 2 +-
> toolchain/helpers.mk | 2 +-
> 8 files changed, 40 insertions(+), 23 deletions(-)
>
Wouldn't it be nice to document this behavior in the manual?
Unless this is considered just an implementation detail.
--
Ezequiel Garcia, VanguardiaSur
www.vanguardiasur.com.ar
next prev parent reply other threads:[~2014-11-24 22:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 16:18 [Buildroot] [PATCH v4 0/9] target permissions Guido Martínez
2014-11-21 16:19 ` [Buildroot] [PATCH v4 1/9] Makefile: don't depend on the umask Guido Martínez
2015-07-13 9:35 ` Arnout Vandecappelle
2015-07-13 10:59 ` Thomas Petazzoni
2014-11-21 16:19 ` [Buildroot] [PATCH v4 2/9] Makefile: don't depend on current skeleton/overlay permissions Guido Martínez
2015-07-13 11:35 ` Arnout Vandecappelle
2015-07-13 11:36 ` [Buildroot] [PATCH] CHANGES: add release note for the permissions Arnout Vandecappelle
2015-07-13 11:39 ` Baruch Siach
2015-07-13 15:03 ` Thomas Petazzoni
2015-07-13 15:02 ` [Buildroot] [PATCH v4 2/9] Makefile: don't depend on current skeleton/overlay permissions Thomas Petazzoni
2014-11-21 16:19 ` [Buildroot] [PATCH v4 3/9] toolchain/helpers.mk: use --chmod on rsync Guido Martínez
2015-07-13 15:07 ` Arnout Vandecappelle
2015-07-13 15:13 ` Thomas Petazzoni
2014-11-21 16:19 ` [Buildroot] [PATCH v4 4/9] pkg-generic.mk: don't depend on external package permissions Guido Martínez
2015-07-13 15:19 ` Thomas Petazzoni
2014-11-21 16:19 ` [Buildroot] [PATCH v4 5/9] package: matchbox-keyboard: use install instead of cp Guido Martínez
2014-11-22 18:47 ` Thomas Petazzoni
2014-11-21 16:19 ` [Buildroot] [PATCH v4 6/9] scripts: mkmakefile: set umask before calling BR's makefile Guido Martínez
2015-07-13 15:20 ` Thomas Petazzoni
2014-11-21 16:19 ` [Buildroot] [PATCH v4 7/9] nitrogen6x: use install instead of cp Guido Martínez
2014-11-21 16:19 ` [Buildroot] [PATCH v4 8/9] boot/grub: " Guido Martínez
2014-11-21 16:19 ` [Buildroot] [PATCH v4 9/9] fs/iso9660: " Guido Martínez
2014-11-22 18:02 ` [Buildroot] [PATCH v4 0/9] target permissions Thomas Petazzoni
2014-11-25 23:01 ` Guido Martínez
2014-11-24 22:17 ` Ezequiel Garcia [this message]
2014-12-03 18:07 ` Guido Martínez
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=5473AE78.1000900@vanguardiasur.com.ar \
--to=ezequiel@vanguardiasur.com.ar \
--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