Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH][RFC] bitbake.conf: use empty SRC_URI by default
Date: Fri, 09 Mar 2012 00:07:44 -0800	[thread overview]
Message-ID: <4F59BA50.3010309@linux.intel.com> (raw)
In-Reply-To: <4F5926DC.2030705@opendreambox.org>

On 03/08/2012 01:38 PM, Andreas Oberritter wrote:
> On 08.03.2012 03:51, Andreas Oberritter wrote:
>> * Otherwise, recipes that only append to SRC_URI instead of
>>    overwriting it will get the full path of the recipe written
>>    into the Source: field of the package.
>>
>> Signed-off-by: Andreas Oberritter<obi@opendreambox.org>
>> ---
>> * I haven't tested this yet, I don't know whether there
>>    are any caveeats. What's the purpose of having ${FILE}
>>    in there, anyway?
>
> Richard, did you commit this by accident? In the meantime I've started a
> clean build with this patch applied and noticed eglibc-locale failing,
> because opkg-build complains about a missing "Source" field.
>
Agreed, this seems to have been committed by accident, we see the same 
failures on the Autobuilder.

Sau!

> Regards,
> Andreas
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>



  reply	other threads:[~2012-03-09  8:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-08  2:51 [PATCH][RFC] bitbake.conf: use empty SRC_URI by default Andreas Oberritter
2012-03-08 21:38 ` Andreas Oberritter
2012-03-09  8:07   ` Saul Wold [this message]
2012-03-09 14:25     ` 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=4F59BA50.3010309@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox