From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 5/5] package: linux-fusion: use install instead of cp
Date: Mon, 17 Nov 2014 23:06:05 +0100 [thread overview]
Message-ID: <546A714D.3040402@mind.be> (raw)
In-Reply-To: <1416244750-24256-6-git-send-email-guido@vanguardiasur.com.ar>
On 17/11/14 18:19, Guido Mart?nez wrote:
> in order to not depend on the previous permissions of the file
>
> Signed-off-by: Guido Mart?nez <guido@vanguardiasur.com.ar>
Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
There are a few more suspicious cp instances:
board/boundarydevices/nitrogen6x/post-build.sh
boot/grub/grub.mk
fs/iso9660/iso9660.mk
Also, it would be good to document somewhere (e.g. in the intro mail) why the
rsync in the toolchain is OK. Or even better, replace it even though it's not
really necessary - it just feels more consistent and safe.
Regards,
Arnout
> ---
> package/linux-fusion/linux-fusion.mk | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/package/linux-fusion/linux-fusion.mk b/package/linux-fusion/linux-fusion.mk
> index c5e7976..001388c 100644
> --- a/package/linux-fusion/linux-fusion.mk
> +++ b/package/linux-fusion/linux-fusion.mk
> @@ -36,8 +36,8 @@ define LINUX_FUSION_INSTALL_TARGET_CMDS
> $(LINUX_FUSION_MAKE_OPTS) \
> INSTALL_MOD_PATH=$(TARGET_DIR) \
> -C $(@D) install
> - mkdir -p $(LINUX_FUSION_ETC_DIR)
> - cp -dpf package/linux-fusion/40-fusion.rules $(LINUX_FUSION_ETC_DIR)
> + $(INSTALL) -D -m 644 package/linux-fusion/40-fusion.rules \
> + $(LINUX_FUSION_ETC_DIR)/40-fusion.rules
> endef
>
> $(eval $(generic-package))
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2014-11-17 22:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 17:19 [Buildroot] [PATCH v3 0/5] Target permissions Guido Martínez
2014-11-17 17:19 ` [Buildroot] [PATCH v3 1/5] Makefile: don't depend on the umask Guido Martínez
2014-11-17 21:11 ` Arnout Vandecappelle
2014-11-18 17:01 ` Guido Martínez
2014-11-18 19:22 ` Arnout Vandecappelle
2014-11-17 21:36 ` Yann E. MORIN
2014-11-17 21:41 ` Arnout Vandecappelle
2014-11-17 21:48 ` Yann E. MORIN
2014-11-17 17:19 ` [Buildroot] [PATCH v3 2/5] Makefile: don't depend on current skeleton/overlay permissions Guido Martínez
2014-11-17 21:39 ` Yann E. MORIN
2014-11-17 17:19 ` [Buildroot] [PATCH v3 3/5] pkg-generic.mk: don't depend on external package permissions Guido Martínez
2014-11-17 21:41 ` Yann E. MORIN
2014-11-18 17:02 ` Guido Martínez
2014-11-17 17:19 ` [Buildroot] [PATCH v3 4/5] package: matchbox-keyboard: use install instead of cp Guido Martínez
2014-11-17 21:44 ` Yann E. MORIN
2014-11-18 17:06 ` Guido Martínez
2014-11-17 17:19 ` [Buildroot] [PATCH v3 5/5] package: linux-fusion: " Guido Martínez
2014-11-17 21:49 ` Yann E. MORIN
2014-11-17 22:06 ` Arnout Vandecappelle [this message]
2014-11-18 17:17 ` Guido Martínez
2014-11-18 19:23 ` Arnout Vandecappelle
2014-11-18 19:40 ` Guido Martínez
2014-11-18 20:58 ` Arnout Vandecappelle
2014-11-18 22:59 ` Thomas Petazzoni
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=546A714D.3040402@mind.be \
--to=arnout@mind.be \
--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 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.