From: "Enrico Scholz" <enrico.scholz@sigma-chemnitz.de>
To: bitbake-devel@lists.openembedded.org
Subject: Support for git+https://foo.example.com like URIs
Date: Thu, 25 Jun 2020 15:42:42 +0200 [thread overview]
Message-ID: <lyh7uzxnvx.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
Hello,
for some years we are using a mechanism which allows to encode the
protocol ("https", "file", ...) within the base uri. So, we can write
| PROJECT_BASE_URI = "git+https://foo.example.com/project"
| SRC_URI = "${PROJECT_BASE_URI}/some-repo"
instead of
| PROJECT_BASE_URI = "git://foo.example.com/project"
| PROJECT_BASE_PROTOCOL = "https"
| SRC_URI = "${PROJECT_BASE_URI}/some-repo;protocol=${PROJECT_BASE_PROTOCOL}"
Four years ago I wrote a bug report [1] with a patch against bitbake
itself which was more or less rejected.
In the meantime, I moved this out in an OE class [2] which overrides
'bb.fetch.decodeurl'.
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}?
Enrico
Footnotes:
[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=9738
[2] https://github.com/sigma-embedded/meta-de.sigma-chemnitz/blob/zeus/classes/elito-uridecode.bbclass
https://github.com/sigma-embedded/meta-de.sigma-chemnitz/blob/zeus/lib/elito/__init__.py
next reply other threads:[~2020-06-25 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 13:42 Enrico Scholz [this message]
2020-06-25 14:44 ` [bitbake-devel] Support for git+https://foo.example.com like URIs Paul Barker
2020-06-25 14:58 ` Enrico Scholz
2020-06-28 7:51 ` Richard Purdie
2020-06-28 9:48 ` Enrico Scholz
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=lyh7uzxnvx.fsf@ensc-virt.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--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.