Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Christian Stewart <christian@paral.in>
Cc: Anisse Astier <anisse@astier.eu>,
	Buildroot Mailing List <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/2] package/go: set GOCACHE for download post-process
Date: Mon, 16 Jan 2023 21:56:37 +0100	[thread overview]
Message-ID: <87edrufbay.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CA+h8R2q16vjmAME02D5rSLyEqRN7BSG=shb6f78z4tNKPJRD5g@mail.gmail.com> (Christian Stewart's message of "Mon, 16 Jan 2023 12:36:50 -0800")

>>>>> "Christian" == Christian Stewart <christian@paral.in> writes:

 > Hi Peter,
 > Thought this was set already!

It is for the build step - but not for the download step, so we can end
up in problems with the go mod vendor call in the download post-process.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-01-16 20:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-16 10:50 [Buildroot] [PATCH 1/2] package/go: set GOCACHE for download post-process Peter Korsgaard
2023-01-16 10:50 ` [Buildroot] [PATCH 2/2] package/go: explicitly set GOMODCACHE Peter Korsgaard
2023-01-16 20:30   ` Yann E. MORIN
2023-01-16 20:52     ` Peter Korsgaard
2023-01-16 20:38   ` Christian Stewart via buildroot
2023-01-16 20:55     ` Peter Korsgaard
2023-01-16 21:35       ` Christian Stewart via buildroot
2023-01-17  9:27   ` Peter Korsgaard
2023-01-16 20:26 ` [Buildroot] [PATCH 1/2] package/go: set GOCACHE for download post-process Yann E. MORIN
2023-01-16 20:36 ` Christian Stewart via buildroot
2023-01-16 20:56   ` Peter Korsgaard [this message]
2023-01-17  9:27 ` Peter Korsgaard

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=87edrufbay.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=anisse@astier.eu \
    --cc=buildroot@buildroot.org \
    --cc=christian@paral.in \
    /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