From: Martin Jansa <martin.jansa@gmail.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: update-alternatives automatic rename happens too late
Date: Wed, 13 Mar 2013 14:35:24 +0100 [thread overview]
Message-ID: <20130313133524.GH3260@jama> (raw)
[-- Attachment #1: Type: text/plain, Size: 610 bytes --]
When using update-alternatives feature to rename targets to
target.${BPN} it happens in perform_packagecopy, but for recipes where
that target is also staged to sysroot it's too late, both recipes will
try to install the same target file to sysroot.
One way to resolve this is to rename target to target.${BPN} directly in
recipe's do_install, but can we move this automatic renaming to
do_install? More importantly do we have some examples where we need to
run u-a for files in sysroot (e.g. when unpacking archive from
sstate-cache)?
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next reply other threads:[~2013-03-13 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 13:35 Martin Jansa [this message]
2013-03-13 15:51 ` update-alternatives automatic rename happens too late Mark Hatle
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=20130313133524.GH3260@jama \
--to=martin.jansa@gmail.com \
--cc=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox