All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-marie Lemetayer <jean-marie.lemetayer@savoirfairelinux.com>
To: Mark Hatle <mark.hatle@kernel.crashing.org>
Cc: paul eggleton <paul.eggleton@linux.intel.com>,
	bitbake-devel <bitbake-devel@lists.openembedded.org>,
	Savoir-faire Linux Rennes <rennes@savoirfairelinux.com>
Subject: Re: [RFC][PATCH 2/2] fetch2/npm.py: refactor the npm fetcher
Date: Wed, 23 Oct 2019 09:07:44 -0400 (EDT)	[thread overview]
Message-ID: <1414446736.248948.1571836064394.JavaMail.zimbra@savoirfairelinux.com> (raw)
In-Reply-To: <4409c36d-23b9-4ddb-d681-5328f75330dc@kernel.crashing.org>

On Oct 22, 2019, at 7:10 PM, Mark Hatle mark.hatle@kernel.crashing.org wrote:
> On 10/22/19 4:04 AM, Jean-Marie LEMETAYER wrote:
>> This commit refactors the npm fetcher to improve some points and fix
>> others:
>> 
>>  - The big change is that the fetcher is only fetching the package
>>    source and no more the dependencies. Thus the npm fetcher act as the
>>    other fetchers e.g git, wget. The dependencies will now be fetched
>>    by the npm class.
> 
> I don't completely understand this and the associated class, but does it work
> with the existing MIRROR and BB_NO_NETWORK/BB_ALLOWED_NETWORKS settings?
> 
> My concern is for people in environments that are not allowed to download except
> from trusted machines, or on disconnected networks so they have everything on a
> local mirror of some sort.
> 
> Additionally with the mirroring, it's not unusual for the name of what is
> downloaded (as well as where it's downloaded from) to change protocol and
> format.  I.e. I'd hope something like:
> 
> .*:.*/.* file://my_local/on/disk/mirror

Thank you for pointing this out. As I was inspired by the wget fetcher, I
think this should be good but i still need to check.

However the npm.bbclass fetches the npm dependencies (currently in the
do_compile task) and this settings are not respected. I am working on a v2
to fix this point.

> I'm also not seeing any test cases for this fetcher.  Since this work isn't well
> understood by most of the regular maintainers, I think it's extremely important
> that test cases are added during any new changes to ensure that the fetcher is
> working properly.

Thank you again. The former npm support does not have any tests so I did not
think about it. I will add some basic tests in the v2.

Regards,
Jean-Marie


  parent reply	other threads:[~2019-10-23 13:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-22  9:04 [RFC][PATCH 0/2] NPM refactoring Jean-Marie LEMETAYER
2019-10-22  9:04 ` [RFC][PATCH 1/2] bitbake: utils.py: add sha384_file and sha512_file Jean-Marie LEMETAYER
2019-10-22  9:04 ` [RFC][PATCH 2/2] fetch2/npm.py: refactor the npm fetcher Jean-Marie LEMETAYER
2019-10-22 17:10   ` Mark Hatle
2019-10-23 13:07     ` Jean-marie Lemetayer
2019-10-23 13:07     ` Jean-marie Lemetayer [this message]
2019-10-23 13:08     ` Jean-marie Lemetayer
2019-10-23 14:27       ` Mark Hatle
2019-10-23 20:12         ` Paul Eggleton
2019-10-23 20:16           ` 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=1414446736.248948.1571836064394.JavaMail.zimbra@savoirfairelinux.com \
    --to=jean-marie.lemetayer@savoirfairelinux.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=mark.hatle@kernel.crashing.org \
    --cc=paul.eggleton@linux.intel.com \
    --cc=rennes@savoirfairelinux.com \
    /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.