All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexander Kanavin" <alex.kanavin@gmail.com>
To: Juergen Landwehr <juergen.landwehr@gmx.de>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] #golang: go fetches dependencies in compile phase
Date: Mon, 12 Apr 2021 16:24:24 +0200	[thread overview]
Message-ID: <CANNYZj8CN=yOMCQG02wErhYtr415xO=H9QT+ptN+t517+0KHTQ@mail.gmail.com> (raw)
In-Reply-To: <7847.1618236117006142456@lists.yoctoproject.org>

[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]

I'd suggest you place that tarball into some artefact storage, and have it
listed in SRC_URI. Then the standard Yocto mechanism for fetching,
checksumming, caching and unpacking tarballs kicks in, so you only need to
make sure the tree is set up correctly after unpacking, maybe with some
simple post-processing.

Alex

On Mon, 12 Apr 2021 at 16:02, Juergen Landwehr <juergen.landwehr@gmx.de>
wrote:

> Hi Alex,
>
> OK, understood.
>
> If the "local download cache path" is well-known (this is not by any
> chance $DL_DIR?), then we could create a tar from the vendor directory
> (which is created when you call "go mod vendor" and contains all the
> downloaded dependencies) and put this tar file into the download cache.
>
> Before actually calling "go mod vendor", we would first check, if there is
> a tar file for the vendor directory in the download cache and if so simply
> unpack the tar.
>
> Does this make sense, or am I too naive and this is just nonsense?
>
> Jürgen
> 
>
>

[-- Attachment #2: Type: text/html, Size: 1360 bytes --]

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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09 13:53 #golang: go fetches dependencies in compile phase juergen.landwehr
2021-04-09 15:19 ` [yocto] " Konrad Weihmann
2021-04-12  8:30   ` Juergen Landwehr
2021-04-12  9:00 ` [yocto] " Robert Berger
2021-04-12 11:47   ` Juergen Landwehr
2021-04-12 12:21     ` [yocto] " Alexander Kanavin
2021-04-12 14:01       ` Juergen Landwehr
2021-04-12 14:24         ` Alexander Kanavin [this message]
2021-04-14 19:30     ` [yocto] " Robert Berger

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='CANNYZj8CN=yOMCQG02wErhYtr415xO=H9QT+ptN+t517+0KHTQ@mail.gmail.com' \
    --to=alex.kanavin@gmail.com \
    --cc=juergen.landwehr@gmx.de \
    --cc=yocto@lists.yoctoproject.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 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.