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] Config.in: add BR2_DL_DIR_OPTS
Date: Thu, 1 Nov 2018 12:18:55 +0100	[thread overview]
Message-ID: <20181101111855.GR28575@scaer> (raw)
In-Reply-To: <20181101120151.4d8e4055@windsurf>

Thomas, All,

On 2018-11-01 12:01 +0100, Thomas Petazzoni spake thusly:
> On Thu, 1 Nov 2018 10:06:16 +0100, Yann E. MORIN wrote:
> > On 2018-10-31 14:39 -0700, Markus Mayer spake thusly:
> > > Provide a simple mechanism to pass extra arguments to "mkdir" when
> > > creating download directories. This can be helpful if one needs the
> > > download directories to be writable multiple users ("shared download
> > > cache").  
> > 
> > In retrospect, I think our enforcing of umask globally is wrong.
> > 
> > It was added in commit bee5745ccc2 (Makefile: don't depend on the umask)
> > under the requirements that modes in target/ be predicatble.
> > 
> > Although that is indeed a good reason, I think we should have instead
> > ensured those modes with a plain chmod on target/ during the
> > target-finalize step.
> 
> But is it possible to have a plain "chmod" on target/ that will
> properly preserve whatever packages have decided to use as permissions
> when installing files ?

Right, but specifying modes at install time is not reliable anyway, as
it is not running root. The reason for explicitly setting permissions at
install time is mostly due to packages wanting to set suid bits, which
can't work. There can be outliers too, but they mostly are corner cases
which should be fixed not to set permissions.

So packages should instead provide FOO_PERMISSIONS, or users should use
permissions tables.

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-11-01 11:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31 21:39 [Buildroot] [PATCH] Config.in: add BR2_DL_DIR_OPTS Markus Mayer
2018-11-01  1:54 ` Carlos Santos
2018-11-01  5:18   ` Markus Mayer
2018-11-01  9:06 ` Yann E. MORIN
2018-11-01 11:01   ` Thomas Petazzoni
2018-11-01 11:18     ` Yann E. MORIN [this message]
2018-11-01 12:19 ` Arnout Vandecappelle
2018-11-01 12:23   ` Yann E. MORIN
2018-11-01 15:16     ` Markus Mayer
2018-11-01 17:04       ` Yann E. MORIN
2019-03-17 12:51 ` 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=20181101111855.GR28575@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