mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Juergen Borleis <jbe@pengutronix.de>
To: Michael Olbrich <m.olbrich@pengutronix.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Root filesystem creation regression
Date: Mon, 22 Jun 2020 11:14:30 +0200	[thread overview]
Message-ID: <202006221114.30583.jbe@pengutronix.de> (raw)
In-Reply-To: <20200622084746.GA23174@pengutronix.de>

Hi Michael,

Michael Olbrich wrote:
> […]
> 'install_tree' is a bit of a special case here. The problem ist, that it
> cannot know, which directories are implicit. So it will always create all
> subdirectories (except the root directory of the tree). So you need to fix
> the permission in the install stage.

I do not want and I do not need to know how "systemd" likes its directories. I 
just want to *add* a file to this directory. And this is how it works if you 
run "make install" in your package for a regular root filesystem: The "install" 
tool just copies a file to this dedicated directory and uses the already 
existing directory (and its permissions) as-is - and everything is fine.
The conflict only happens in PTXdist due to all install stages always install 
into an "empty" filesystem.

jb

-- 
Pengutronix e.K.                       | Juergen Borleis             |
Steuerwalder Str. 21                   | https://www.pengutronix.de/ |
31137 Hildesheim, Germany              | Phone: +49-5121-206917-128  |
Amtsgericht Hildesheim, HRA 2686       | Fax:   +49-5121-206917-9    |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de

  reply	other threads:[~2020-06-22  9:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22  7:55 Juergen Borleis
2020-06-22  8:47 ` Michael Olbrich
2020-06-22  9:14   ` Juergen Borleis [this message]
2020-06-22 12:37     ` Michael Olbrich

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=202006221114.30583.jbe@pengutronix.de \
    --to=jbe@pengutronix.de \
    --cc=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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