All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Christian Stewart via buildroot <buildroot@buildroot.org>
Cc: Anisse Astier <anisse@astier.eu>,
	"Yann E . MORIN" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] [PATCH-NEXT v3 4/6] support/download/go-post-process: implement Go vendoring support
Date: Thu, 6 Jan 2022 22:08:24 +0100	[thread overview]
Message-ID: <20220106220824.31306aa6@windsurf> (raw)
In-Reply-To: <20211010234655.585526-4-christian@paral.in>

Hello,

On Sun, 10 Oct 2021 16:46:53 -0700
Christian Stewart via buildroot <buildroot@buildroot.org> wrote:

> +# Do the Go vendoring
> +pushd ${base_name} > /dev/null
> +# modcacherw option leaves directories in the module cache at their default
> +# permissions rather than making them read-only.
> +if [ ! -f go.mod ] && [ -n "${gomod_init}" ]; then
> +    go mod init -modcacherw ${gomod_init}

So here you're using "go mod init" to create the go.mod file, but in
package/pkg-golang.mk, we're manually creating it.

So for the sake of consistency, I tried using "go mod init" in
package/pkg-golang.mk as well, but running that on balena-engine caused
go mod init to start downloading stuff... which is wrong because
balena-engine already comes with its vendored dependencies.

So in the end, I ended up creating the go.mod manually (with the same
logic) in both pkg-golang.mk and in this download post-process script.
But if we find why "go mod init" didn't work in the context of
pkg-golang.mk, we could switch back to using that.

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2022-01-06 21:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-10 23:46 [Buildroot] [PATCH-NEXT v3 1/6] support/download/dl-wrapper: add concept of download post-processing Christian Stewart via buildroot
2021-10-10 23:46 ` [Buildroot] [PATCH-NEXT v3 2/6] package/pkg-download.mk: add <pkg>_DOWNLOAD_POST_PROCESS variable Christian Stewart via buildroot
2021-10-10 23:46 ` [Buildroot] [PATCH-NEXT v3 3/6] support/download/post-process-helpers: add helper function for post process scripts Christian Stewart via buildroot
2021-10-10 23:46 ` [Buildroot] [PATCH-NEXT v3 4/6] support/download/go-post-process: implement Go vendoring support Christian Stewart via buildroot
2022-01-06 10:32   ` Thomas Petazzoni
2022-01-06 21:08   ` Thomas Petazzoni [this message]
2022-01-06 21:20     ` Christian Stewart via buildroot
2022-01-07  0:45       ` Christian Stewart via buildroot
2021-10-10 23:46 ` [Buildroot] [PATCH-NEXT v3 5/6] package/embiggen-disk: new package Christian Stewart via buildroot
2021-10-10 23:46 ` [Buildroot] [PATCH-NEXT v3 6/6] package/gocryptfs: " Christian Stewart via buildroot
2021-10-11  7:04 ` [Buildroot] [PATCH-NEXT v3 1/6] support/download/dl-wrapper: add concept of download post-processing Thomas Petazzoni
2021-10-11  7:13   ` Christian Stewart via buildroot
2021-10-14 21:15     ` Thomas Petazzoni
2022-01-06 21:05 ` Thomas Petazzoni

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=20220106220824.31306aa6@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=anisse@astier.eu \
    --cc=buildroot@buildroot.org \
    --cc=yann.morin.1998@free.fr \
    /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.