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 11:32:58 +0100 [thread overview]
Message-ID: <20220106113258.36ce7f11@windsurf> (raw)
In-Reply-To: <20211010234655.585526-4-christian@paral.in>
Hello Christian,
On Sun, 10 Oct 2021 16:46:53 -0700
Christian Stewart via buildroot <buildroot@buildroot.org> wrote:
> From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
>
> This commit introduces the download post-process script
> support/download/go-post-process, and hooks it into the Go package
> infrastructure.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> Signed-off-by: Christian Stewart <christian@paral.in>
>
> v1 -> v2:
>
> - re-submitting Thomas's series with adjustments:
> - run "go mod init" just before "go mod vendor"
> - this fixes the case when go.mod does not exist
> - use -modcacherw to fix "make clean" permissions errors
> - use the mk_tar_gz helper in the post-process step
>
> Signed-off-by: Christian Stewart <christian@paral.in>
I am a bit confused by the changes you introduced here. You're
labelling this patch series v3, so I assume it comes after my v2:
https://patchwork.ozlabs.org/project/buildroot/patch/20201219153525.1361175-6-thomas.petazzoni@bootlin.com/
I'm particularly confused by the addition of the -g option to pass the
argument of "go mod init" as opposed to using the BR_GOMOD environment
variable.
In the patch I linked above, you reported that it was causing some hash
issues, but I don't understand which of your changes fixed that
problem. Could you clarify?
Also, my patch dropped the creation of go.mod from
package/pkg-golang.mk (macro $(2)_GEN_GOMOD), but I'm not sure why your
patch doesn't drop 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
next prev parent reply other threads:[~2022-01-06 10:33 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 [this message]
2022-01-06 21:08 ` Thomas Petazzoni
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=20220106113258.36ce7f11@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox