From: "Bernhard Reutner-Fischer" <rep.dot.nop@gmail.com>
To: lei yang <yanglei.fage@gmail.com>, Chris Larson <clarson@kergoth.com>
Cc: "bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [bitbake-devel] git address in SRC_URI, doesn't works for me
Date: Sun, 20 Jan 2013 15:05:48 +0100 [thread overview]
Message-ID: <13c58476de5.2760.0f39ed3bcad52ef2c88c90062b7714dc@gmail.com> (raw)
In-Reply-To: <CAHsH0E_9kaYC0_9rv+zHR8FwxXyU=7vTj2eL85_jJ=uRtb0aSw@mail.gmail.com>
On 20 January 2013 07:08:35 lei yang <yanglei.fage@gmail.com> wrote:
> On Sun, Jan 20, 2013 at 10:15 AM, Chris Larson <clarson@kergoth.com> wrote:
> >
> > On Sat, Jan 19, 2013 at 2:13 AM, lei yang <yanglei.fage@gmail.com> wrote:
> >>
> >> SRC_URI = "git://git.opensvc.com/multipath-tools/.git;protocol=http"
> >> it doe noting,and trying to find COPING,but it doesn't clone it
> >
> >
> > This is the correct syntax. The URL scheme (git://) determines what bitbake
> > fetcher, and therefore what tool, is used to fetch. If you use http://,
> > it'll try to download it with wget, not git.
> > -
>
>
> Correct, now it works for me, what protocol determines, , I thought
> SRC_URS="address;protocol=*"
> The address should be a real address, now I know it's not , a strange usage
Yes, it is very counterintuitive (but cannot be corrected easily due to
gazillions of recipes that use this unfortunate scheme).
Sent with AquaMail for Android
http://www.aqua-mail.com
next prev parent reply other threads:[~2013-01-20 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 9:13 git address in SRC_URI, doesn't works for me lei yang
2013-01-20 2:15 ` [bitbake-devel] " Chris Larson
2013-01-20 4:27 ` lei yang
2013-01-20 6:08 ` lei yang
2013-01-20 14:05 ` Bernhard Reutner-Fischer [this message]
2013-01-20 20:07 ` Chris Larson
2013-01-22 10:36 ` Paul Eggleton
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=13c58476de5.2760.0f39ed3bcad52ef2c88c90062b7714dc@gmail.com \
--to=rep.dot.nop@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=clarson@kergoth.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yanglei.fage@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