From: Mark Hatle <mark.hatle@kernel.crashing.org>
To: vishwanath Chandapur <vishwavtu@gmail.com>, poky@lists.yoctoproject.org
Subject: Re: [poky] clarification on 'gitsm://' fetcher.
Date: Thu, 22 Feb 2024 11:58:44 -0600 [thread overview]
Message-ID: <778ff323-f8b3-4991-86ef-5e2b3050c8d3@kernel.crashing.org> (raw)
In-Reply-To: <ixbV.1708072376356310245.WNd3@lists.yoctoproject.org>
On 2/16/24 2:32 AM, vishwanath Chandapur wrote:
> Hi
>
> In recent grpc recipe has changed to gitsm:// from git:// because of which now
> all submodules are downloaded even though all may not require.
>
> My question not to grpc recipes but in general when a recipe uses gitstm may
> have these two issues.
>
> 1. Unnecessarily some of the submodules/packages have to be maintained in
> localmirror even though it is not required.
In gitsm mode, where the .submodules file is used, how/who defines what is and
isn't required? As far as I know it's used or it's not.
To my knowledge, when you run git submodule, anything in .submodules is
processed. Thus they are all 'required'. Move from gitsm:// to git:// says
"I'm never going to use the .submodule file", and thus moves this ownership from
the repository owner (.submodule file) to the recipe owner.
> 2. Most importantly, if a submodule/package is enabled by default internally,
> the package will not appear in the final manifest file and miss out in the final
> SBOM file.
If the submodules are not part of the SBOM, then it's a bug in the SBOM
creation. This is a separate issue, one that should be identified and fixed.
--Mark
>
> Regards
> Vishwa
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#13254): https://lists.yoctoproject.org/g/poky/message/13254
> Mute This Topic: https://lists.yoctoproject.org/mt/104389390/3616948
> Group Owner: poky+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/poky/unsub [mark.hatle@kernel.crashing.org]
> -=-=-=-=-=-=-=-=-=-=-=-
>
prev parent reply other threads:[~2024-02-22 17:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 8:32 clarification on 'gitsm://' fetcher vishwanath Chandapur
2024-02-22 17:58 ` Mark Hatle [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=778ff323-f8b3-4991-86ef-5e2b3050c8d3@kernel.crashing.org \
--to=mark.hatle@kernel.crashing.org \
--cc=poky@lists.yoctoproject.org \
--cc=vishwavtu@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).