From: "Enrico Scholz" <enrico.scholz@sigma-chemnitz.de>
To: "Richard Purdie" <richard.purdie@linuxfoundation.org>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] Support for git+https://foo.example.com like URIs
Date: Sun, 28 Jun 2020 11:48:03 +0200 [thread overview]
Message-ID: <lyy2o7cyi4.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <099ddfc8784d7760adb9b1fdd8207325d29895dc.camel@linuxfoundation.org> (Richard Purdie's message of "Sun, 28 Jun 2020 08:51:43 +0100")
"Richard Purdie" <richard.purdie@linuxfoundation.org> writes:
>> > PROJECT_BASE_URI = "git+https://foo.example.com/project"
>>
>> Is there some generic interest in this functionality so that I can
>> create and send a patch for bitbake? Or is this too special and
>> people are happy with altering ${MIRROR}?
>
> I didn't (and don't) like writing special cases into general code.
mmmh... In my original report you complained that code is not generic
enough and works for git only. Now, that is has been generalized, you
say it is too generic...
> My intent has always been (and still is) to see if a more generic
> solution is possible which not only addresses your use case but the
> ones others have as well.
>
> That will likely mean using the mirrors variable to remap things which
> will be slightly more complex but will also enable others.
I do not think, that bothering around with mirrors (or better PREMIRRORS)
is any helpful for this cases. In 99% of cases, people want to set http://
or perhaps ssh:// as a transport protocol.
People want to completely rewrite an uri; they do not want to try another
one first and then another one. This is nothing which can be solved by
mirrors; especially when you start to use AUTOREV.
Enrico
next prev parent reply other threads:[~2020-06-28 9:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 13:42 Support for git+https://foo.example.com like URIs Enrico Scholz
2020-06-25 14:44 ` [bitbake-devel] " Paul Barker
2020-06-25 14:58 ` Enrico Scholz
2020-06-28 7:51 ` Richard Purdie
2020-06-28 9:48 ` Enrico Scholz [this message]
2020-06-28 10:10 ` 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=lyy2o7cyi4.fsf@ensc-virt.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=bitbake-devel@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.