From: Patrick Ohly <patrick.ohly@intel.com>
To: "Dominig ar Foll (Intel Open Source)" <dominig.arfoll@fridu.net>
Cc: yocto@yoctoproject.org
Subject: Re: Changing UID GID
Date: Wed, 15 Feb 2017 15:57:58 +0100 [thread overview]
Message-ID: <1487170678.13854.411.camel@intel.com> (raw)
In-Reply-To: <c5a4c802-163e-6e4b-e7c2-fc2f598c11ec@fridu.net>
On Wed, 2017-02-15 at 15:43 +0100, Dominig ar Foll (Intel Open Source)
wrote:
> Hello,
>
> in AGL project we are facing an issue as when we create new images the
> UID,GID of given packages can (and does) change depending of the
> build.
> This induces issues when we create partial update file using image
> diffs.
Is that for partial updates with OSTree or something else?
> Could you let us know if we need to create our own solution, or if
> yocto already has a model to enforce a known UID-GID on packages
> coming from internal or external repo such as Open-Embedded without
> patching (or creating a bbappend) for each imported package ?
There's useradd-staticids.bbclass in OE-core, see
https://github.com/ostroproject/ostro-os/blob/master/meta-ostro/conf/distro/ostro.conf#L179 for an example how that was used.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2017-02-15 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 14:43 Changing UID GID Dominig ar Foll (Intel Open Source)
2017-02-15 14:55 ` Joshua Lock
2017-02-15 14:57 ` Patrick Ohly [this message]
2017-02-17 9:58 ` Changing UID GID (thaks) Dominig ar Foll (Intel Open Source)
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=1487170678.13854.411.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=dominig.arfoll@fridu.net \
--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.