From: "Christian Lindeberg" <christian.lindeberg@axis.com>
To: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH v2 2/2] fetch2: Add gomodgit fetcher
Date: Tue, 10 Sep 2024 02:32:41 -0700 [thread overview]
Message-ID: <30802.1725960761219204467@lists.openembedded.org> (raw)
In-Reply-To: <79ff6187-aa9e-4dc7-bd79-4f37e1603bb9@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]
On Sat, Sep 7, 2024 at 09:27 AM, Vyacheslav Yurkov wrote:
>
> A few questions on the patchset.
>
> - What if the module doesn't use any proxy? (E.g. hosted in a private
> repository)
>
The gomodgit fetcher is for git repositories that needs to use the direct mode.
(Cf. https://go.dev/ref/mod#private-module-proxy-direct) ( https://go.dev/ref/mod#private-module-proxy-direct= )
>
> - The current recipetool approach ( https://git.openembedded.org/openembedded-core/tree/scripts/lib/recipetool/create_go.py
> ) uses vendoring approach and all dependencies go into the SRC_URI. Thus
> it's required to populate the required license information for the
> manifest generation. Would that be possible with this fetcher as well?
>
Yes, there would be no change when creating or updating the ${BPN}-licenses.inc
file compared to the vendoring approach. And then the gomod:// and gomodgit://
URLs would go into ${BPN}-modules.inc.
>
>
> Slava
>
>
Thanks,
Christian
[-- Attachment #2: Type: text/html, Size: 1465 bytes --]
prev parent reply other threads:[~2024-09-10 9:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 9:27 [PATCH v2 1/2] fetch2: Add gomod fetcher Christian Lindeberg
2024-09-06 9:27 ` [PATCH v2 2/2] fetch2: Add gomodgit fetcher Christian Lindeberg
2024-09-07 7:27 ` [bitbake-devel] " Vyacheslav Yurkov
2024-09-10 9:32 ` Christian Lindeberg [this message]
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=30802.1725960761219204467@lists.openembedded.org \
--to=christian.lindeberg@axis.com \
--cc=bitbake-devel@lists.openembedded.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.