Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mike Crowe" <yocto@mac.mcrowe.com>
To: openembedded-core@lists.openembedded.org
Subject: archiver.bbclass and fetch2/npmsw.py
Date: Mon, 12 Apr 2021 15:41:19 +0100	[thread overview]
Message-ID: <20210412144119.GA18594@mcrowe.com> (raw)

We have a class that stores the files in ${DL_DIR} that are required for
each recipe so they can be made available in ${DL_DIR} later. This is a bit
like archiver.bbclass, but not quite the same.

I'm having trouble making our class work for recipes that use the post
refactor[1] npm.bbclass and the npmsw fetcher in Dunfell. The individual
dependency paths aren't returned by bb.fetch2.Fetch's localpaths method.

I hoped that I could see how archiver.bbclass solved this problem, so I
tried running do_ar_mirror for the recipe and got:

NOTE: Using original download: [...]/package.json
NOTE: Copying source mirror
NOTE: Archiving url: npmsw:///[...]/npm-shrinkwrap.json
NOTE: Using original download: /home/mac/src/oe/build/downloads/
NOTE: Copying source mirror
DEBUG: Python function do_ar_mirror finished

and the whole of my downloads directory ends up copied to
${WORKDIR}/archiver-sources . :(

It looks like archiver.bbclass doesn't know the dependency filenames (or
subdirectories) either because NpmShrinkWrap doesn't expose them via a
localpath method.

It didn't look like there was an easy fix for this since everyone else
expects the localpath method to return only one path. I'm hoping that I
might have missed something. Does anyone have any advice?

Thanks.

Mike.

[1] oe-core:fb2252ee0777c6d26dea94c7588c323a6b97e961

                 reply	other threads:[~2021-04-12 14:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210412144119.GA18594@mcrowe.com \
    --to=yocto@mac.mcrowe.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