All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Giuseppe Condorelli <giuseppe.condorelli@gmail.com>
Cc: openembedded-devel@lists.openembedded.org,
	openembedded-core@lists.openembedded.org
Subject: Re: [oe] Packages broken URL
Date: Tue, 15 May 2012 14:45:30 +0100	[thread overview]
Message-ID: <7192456.4O7Cf6LSyd@helios> (raw)
In-Reply-To: <CAOHjBZv+ox9dJh+g1rjFqqnYvcQvLuRboV8ANZssKXTv0NSO7Q@mail.gmail.com>

On Tuesday 15 May 2012 15:36:37 Giuseppe Condorelli wrote:
>On Tuesday 15 May 2012 07:30:48 Gary Thomas wrote:
>> On 2012-05-15 07:19, Giuseppe Condorelli wrote:
>> > For example building git-1.7.7 fails fetching the source.
>>
>> Works fine for me:
>> ...
>
> That's right, but why the git.inc contains a undownloadable url?

This should probably be fixed by moving the SRC_URI from the .bb to the .inc, 
yes.

> This can create a mistake in my opinion.

Only if you create your own recipe that uses git.inc but doesn't set its own 
SRC_URI; the current 1.7.7 recipe does set one.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



WARNING: multiple messages have this Message-ID (diff)
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Giuseppe Condorelli <giuseppe.condorelli@gmail.com>
Cc: openembedded-devel@lists.openembedded.org,
	openembedded-core@lists.openembedded.org
Subject: Re: [oe-core] Packages broken URL
Date: Tue, 15 May 2012 14:45:30 +0100	[thread overview]
Message-ID: <7192456.4O7Cf6LSyd@helios> (raw)
In-Reply-To: <CAOHjBZv+ox9dJh+g1rjFqqnYvcQvLuRboV8ANZssKXTv0NSO7Q@mail.gmail.com>

On Tuesday 15 May 2012 15:36:37 Giuseppe Condorelli wrote:
>On Tuesday 15 May 2012 07:30:48 Gary Thomas wrote:
>> On 2012-05-15 07:19, Giuseppe Condorelli wrote:
>> > For example building git-1.7.7 fails fetching the source.
>>
>> Works fine for me:
>> ...
>
> That's right, but why the git.inc contains a undownloadable url?

This should probably be fixed by moving the SRC_URI from the .bb to the .inc, 
yes.

> This can create a mistake in my opinion.

Only if you create your own recipe that uses git.inc but doesn't set its own 
SRC_URI; the current 1.7.7 recipe does set one.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2012-05-15 13:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15 13:02 [oe-core] Packages broken URL Giuseppe Condorelli
2012-05-15 13:06 ` [oe] " Martin Jansa
2012-05-15 13:06   ` [oe-core] " Martin Jansa
2012-05-15 13:13   ` [oe] " Marko Lindqvist
2012-05-15 19:09     ` Richard Purdie
2012-05-15 13:49   ` [oe-core] " Apelete Seketeli
2012-05-15 13:17 ` Gary Thomas
2012-05-15 13:19   ` Giuseppe Condorelli
2012-05-15 13:30     ` Gary Thomas
2012-05-15 13:36       ` Giuseppe Condorelli
2012-05-15 13:45         ` Paul Eggleton [this message]
2012-05-15 13:45           ` 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=7192456.4O7Cf6LSyd@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=giuseppe.condorelli@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-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.