All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Burton, Ross" <ross.burton@intel.com>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: Yocto-mailing-list <yocto@yoctoproject.org>
Subject: Re: permissions when installing scripts
Date: Mon, 15 Oct 2018 13:35:26 +0100	[thread overview]
Message-ID: <CAJTo0LYbBU4s7w7TEDJwt6Wp8Vr9bsFCxmf1WYM-sX_=5wWkDA@mail.gmail.com> (raw)
In-Reply-To: <CAAfyv36x=np5fcK96ozCHoXe-CFjvpMTdJDA4shpXBMRvd10Hg@mail.gmail.com>

As you've discovered, cp doesn't preserve permissions.  Using install
-m755 is the idiom.

Ross
On Mon, 15 Oct 2018 at 11:12, Belisko Marek <marek.belisko@gmail.com> wrote:
>
> Hi,
>
> I have package which contains bunch of scripts (with +x flag for
> user). When installed in do_install method (simply by copying them to
> destination) they loose +x flag. I know copying directly is not best
> approach but there exists better way how to keep scripts permissions
> like in repo (except calling install -m 755 for all of them)? Thanks.
>
> BR,
>
> marek
>
> --
> as simple and primitive as possible
> -------------------------------------------------
> Marek Belisko - OPEN-NANDRA
> Freelance Developer
>
> Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
> Tel: +421 915 052 184
> skype: marekwhite
> twitter: #opennandra
> web: http://open-nandra.com
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


  reply	other threads:[~2018-10-15 12:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-15 10:11 permissions when installing scripts Belisko Marek
2018-10-15 12:35 ` Burton, Ross [this message]
2018-10-15 18:45   ` Bas Mevissen
2018-10-15 18:53     ` Belisko Marek
2018-10-15 18:53     ` Burton, Ross
2018-10-15 19:02       ` Bas Mevissen

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='CAJTo0LYbBU4s7w7TEDJwt6Wp8Vr9bsFCxmf1WYM-sX_=5wWkDA@mail.gmail.com' \
    --to=ross.burton@intel.com \
    --cc=marek.belisko@gmail.com \
    --cc=yocto@yoctoproject.org \
    /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.