public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v3] wic-image: Fix up file ownership in isar repo after wic run
Date: Thu, 23 Aug 2018 14:29:22 +0200	[thread overview]
Message-ID: <1eaa7390-2466-bd3b-5fe0-4423f2689190@siemens.com> (raw)
In-Reply-To: <20180823122641.237d3oob2yd7373r@MD1KR9XC.ww002.siemens.net>

On 2018-08-23 14:26, [ext] Christian Storm wrote:
> Hi Jan,
> 
>> This prevents needlessly leaving the __pycache__ directories root-owned
>> behind after running wic as superuser - will only cause troubles to the
>> user when trying to clean up the isar repo.
> 
> Hm, why not avoid creating those in the first place? I doubt that the
> binary cache brings us that much performance benefit in our use cases.
> Granted, you have to put/inject
>    export PYTHONDONTWRITEBYTECODE=1
> into *all* environments calling python so that not bothering with it at
> all and removing/chown'ing them post-mortem might be easier or less
> invasive.. Well....

Currently, that does not hurt (tried that first), but I wasn't sure 
about third-party plugins or future upstream stuff.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2018-08-23 12:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-23 12:12 Jan Kiszka
2018-08-23 12:26 ` Christian Storm
2018-08-23 12:29   ` Jan Kiszka [this message]
2018-08-27 22:14 ` Maxim Yu. Osipov
2018-09-12 12:49 ` Henning Schild
2018-09-12 13:22   ` Jan Kiszka

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=1eaa7390-2466-bd3b-5fe0-4423f2689190@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=isar-users@googlegroups.com \
    /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