All of lore.kernel.org
 help / color / mirror / Atom feed
From: richard.purdie@linuxfoundation.org
To: zboszor@pr.hu, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/2] staging.bbclass: Ignore installing multiple symlinks of the same name
Date: Fri, 13 May 2022 15:14:37 +0100	[thread overview]
Message-ID: <c9f06343ae9ba6ab346046539f0daa6a62bc3da0.camel@linuxfoundation.org> (raw)
In-Reply-To: <c97c1296-81b6-5900-eadd-dc3f711e82b2@pr.hu>

On Fri, 2022-05-13 at 16:02 +0200, Zoltan Boszormenyi via
lists.openembedded.org wrote:
> 2022. 05. 13. 15:55 keltezéssel, Alexander Kanavin írta:
> > Apologies, but special-casing this in staging class is not right
> > either. The problem should be addressed at the making of
> > sysroot-destdir/ step from the npm class.
> 
> npm.bbclass creates the symlink in sysroot-destdir for recipe A
> 
> But then it's the job of staging.bbclass to populate a recipe B's
> recipe-sysroot and recipe-sysroot-native from recipe A.
> 
> How can this be worked around from npm.bbclass?

You could move the line from npm.bbclass into the node recipe so it is
only created once?

Cheers,

Richard


      reply	other threads:[~2022-05-13 14:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13 13:48 Fix some NPM related problems Zoltan Boszormenyi
2022-05-13 13:48 ` [PATCH 1/2] npm.bbclass: Fix file permissions before opening it for writing Zoltan Boszormenyi
2022-05-13 13:52   ` [OE-core] " Alexander Kanavin
     [not found]     ` <b47fd784-6d1d-4c89-a61a-d517210ac41a@gmail.com>
2022-05-13 14:00       ` Alexander Kanavin
2022-05-13 13:48 ` [PATCH 2/2] staging.bbclass: Ignore installing multiple symlinks of the same name Zoltan Boszormenyi
2022-05-13 13:55   ` [OE-core] " Alexander Kanavin
2022-05-13 14:02     ` Zoltan Boszormenyi
2022-05-13 14:14       ` richard.purdie [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=c9f06343ae9ba6ab346046539f0daa6a62bc3da0.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=zboszor@pr.hu \
    /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.