All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: liezhi.yang@windriver.com,
	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 16:47:26 +0100	[thread overview]
Message-ID: <3aa94aeeff9cac08cd02fb534b8fe7fff91b211d.camel@linuxfoundation.org> (raw)
In-Reply-To: <b1399680-6f22-4477-ada4-8a718f807237@windriver.com>

On Wed, 2024-05-15 at 17:57 +0800, Robert Yang via lists.openembedded.org wrote:
> 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.

I'm with Quentin, the SRC_URIs should be fixed or this should be in
repo specific codepaths. We're not adding a workaround like that into
the git fetcher.

Cheers,

Richard


      parent reply	other threads:[~2024-05-15 15:47 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
2024-05-15 10:15       ` Quentin Schulz
2024-05-15 15:47       ` Richard Purdie [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=3aa94aeeff9cac08cd02fb534b8fe7fff91b211d.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=liezhi.yang@windriver.com \
    --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 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.