Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: update-alternatives automatic rename happens too late
Date: Wed, 13 Mar 2013 10:51:07 -0500	[thread overview]
Message-ID: <5140A06B.8090904@windriver.com> (raw)
In-Reply-To: <20130313133524.GH3260@jama>

On 3/13/13 8:35 AM, Martin Jansa wrote:
> 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)?
>

It was specifically NOT done via a do_install(_append) because other things 
could have been appending and doing odd behaviors that may or may not be supported.

Also as far as the sysroot went, all of the files that collided were 
executables, man pages, etc... (not libraries or headers!)  so they generally 
are not used during the compilation process, but I can see with the additional 
sysroot checking that this can add problems.

Perhaps the right fix is to add an additional task before the do_package (where 
the sysroot is setup) but after the do_install that is specific to the 
update-alternatives configuration?  Change from doing it in the ${D} directory 
as well...

--Mark



      reply	other threads:[~2013-03-13 16:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13 13:35 update-alternatives automatic rename happens too late Martin Jansa
2013-03-13 15:51 ` Mark Hatle [this message]

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=5140A06B.8090904@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=martin.jansa@gmail.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