All of lore.kernel.org
 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: eglibc 2.13 upgrade
Date: Thu, 28 Apr 2011 15:03:37 -0700	[thread overview]
Message-ID: <4DB9E439.5020009@linux.intel.com> (raw)
In-Reply-To: <BANLkTikjpjVK40B4OO6a4BqB3ys_7hxbmA@mail.gmail.com>

On 04/27/2011 01:13 PM, Khem Raj wrote:
> On Wed, Apr 27, 2011 at 9:44 AM, Koen Kooi<koen@dominion.thruhere.net>  wrote:
>> Why not move those srcrevs into the recipe? IIRC these ones aren't affected by RPs concerns
>
> I am ok doing that but here
> http://lists.linuxtogo.org/pipermail/openembedded-core/2011-April/001536.html
>
> it seems we still need to investigate it before we start moving
> SRCREVs to recipes.
>
We are days away from having this implemented (early next week is the 
plan right now). Once you see the big pull that moves SRCREVs, then you 
can go ahead with your upgrade.

Also creating a new recipe instead of moving the old one will cause a 
lose of history in git, we would prefer moves or create new / delete.

Sau!

>>
>> Op 27 apr. 2011 om 18:21 heeft Khem Raj<raj.khem@gmail.com>  het volgende geschreven:
>>
>>> Hi
>>>
>>> I have eglibc 2.13 upgrade done locally and has been building fine for
>>> all architectures. I have added 2.13 recipes and not
>>> deleted the 2.12, This works ok except when setting the SRCREV. Since
>>> we have a single file called
>>> conf/distro/include/poky-default-revisions.inc to store this
>>> information there can not be two SRCREV for two versions of same
>>> package unless we move them to
>>> recipes which is under work but not yet done. Thats one reason to hold
>>> these patches. I can propose them if we are ok with
>>> removing 2.12 recipes then it becomes straight forward
>>>
>>> Opinions ?
>>>
>>> -Khem
>>>
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core



  reply	other threads:[~2011-04-28 22:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27 16:21 eglibc 2.13 upgrade Khem Raj
2011-04-27 16:44 ` Koen Kooi
2011-04-27 20:13   ` Khem Raj
2011-04-28 22:03     ` Saul Wold [this message]
2011-04-28 22:30       ` Khem Raj
2011-04-30 22:12         ` Khem Raj
2011-05-04 22:50       ` Khem Raj

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=4DB9E439.5020009@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 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.