From: Robert Yang <liezhi.yang@windriver.com>
To: Quentin Schulz <quentin.schulz@cherry.de>,
bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] [PATCH 1/1] fetch2/git.py: Try without '.git' suffix firstly
Date: Wed, 15 May 2024 17:57:56 +0800 [thread overview]
Message-ID: <b1399680-6f22-4477-ada4-8a718f807237@windriver.com> (raw)
In-Reply-To: <367b25fc-4d5a-4a1f-a259-55e2325e1a34@cherry.de>
Hi Quentin,
On 5/15/24 17:35, Quentin Schulz wrote:
> Hi Robert,
>
> On 5/15/24 11:26 AM, Robert Yang via lists.openembedded.org wrote:
>> From: Robert Yang <liezhi.yang@windriver.com>
>>
>> If the repo on server is foo.git, both of the following commands
>> will work:
>> 1) $ git clone <url>/foo.git
>> 2) $ git clone <url>/foo
>> But only the second command works if the repo server is foo
>> (without .git suffix), so try without '.git' suffix firstly.
>>
>
> Shouldn't the SRC_URI in the recipe be fixed instead of the git fetcher? Which
> use case do we need to support here? Something to do with mirroring maybe
The usage is related to repo command + http/https mirror:
* The foo.git on http/https MIRROR works with do_fetch
* But 'repo' command always add a '.git' suffix to the reponame, the foo.git
will be saved as foo.git.git on local disk, and do_fetch would not work with
the local mirror.
Our solution is rename foo.git to foo on http/https mirror, and apply this patch
to make both http(s) and local mirror work with repo command.
It's a little special to our Wind River Linux, and we need send the patch to
mailing list for Yocto compliance.
// Robert
>
> Cheers,
> Quentin
next prev parent reply other threads:[~2024-05-15 9:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 9:26 [PATCH 0/1] fetch2/git.py: Try without '.git' suffix firstly liezhi.yang
2024-05-15 9:26 ` [PATCH 1/1] " liezhi.yang
2024-05-15 9:35 ` [bitbake-devel] " Quentin Schulz
2024-05-15 9:57 ` Robert Yang [this message]
2024-05-15 10:15 ` Quentin Schulz
2024-05-15 15:47 ` Richard Purdie
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=b1399680-6f22-4477-ada4-8a718f807237@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=quentin.schulz@cherry.de \
/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).