As I already explained, the url scheme determines the tool to be used.
http:// will call wget. git:// will call git. protocol= controls the
underlying protocol it's fetched over. Not that complex. The alternative
would be to reverse them, meaning you'd have to tell bitbake not to use
wget for a htt
On 20 January 2013 07:08:35 lei yang wrote:
On Sun, Jan 20, 2013 at 10:15 AM, Chris Larson wrote:
>
> On Sat, Jan 19, 2013 at 2:13 AM, lei yang 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
>
On Sun, Jan 20, 2013 at 10:15 AM, Chris Larson wrote:
>
> On Sat, Jan 19, 2013 at 2:13 AM, lei yang 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
On Sun, Jan 20, 2013 at 10:15 AM, Chris Larson wrote:
>
> On Sat, Jan 19, 2013 at 2:13 AM, lei yang 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
On Sat, Jan 19, 2013 at 2:13 AM, lei yang 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
