All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: Yocto Project Discussion <yocto@yoctoproject.org>
Subject: Re: Recipes updates planned for 1.0
Date: Thu, 11 Nov 2010 20:46:43 -0500	[thread overview]
Message-ID: <4CDC9C83.7020506@windriver.com> (raw)
In-Reply-To: <4CDC8704.9020506@linux.intel.com>

On 10-11-11 7:15 PM, Saul Wold wrote:
>
> Distro / User Space Folks:
>
> Attached is a spread sheet that shows the recipes we plan to update for
> the 1.0 release. This list is based on the reorganization that will be
> coming into master soon and shows that there are 231 recipes that need
> updating and another 93 recipes that need some manual investigation due
> to the checkpkg task not able to determine the version.

I couldn't easily read the CSV in my email, but I scanned
for kernel elements.

I can't tell, are we updating kexec to 2.0.1 ? If so, that's
good. kexec is pretty tightly coupled to the kernel version, I'd
suggest doing it last, or not doing it at all. I'm talking
less about x86 here and more about non-x86. There are more
patches to the 2.0.x version that we can apply in this area,
but unless we have a test-per arch, it is more than likely
broken.

Other related / coupled kernel -> userspace apps appear to be
at the correct versions.

Cheers,

Bruce

>
> For the first phase, we will focus on updating as many of these that can
> be managed, many of these are dot.dot updates and should be easy. The
> focus will be on toolchain, core utilities and libraries, along with the
> graphics core (Xorg and Qt).
>
> We will continue to focus on making sure that LICENSE and
> LIC_FILES_CHKSUM metadata is correct, along with adding URI checksums.
>
> Thanks to all for working on this effort.



      reply	other threads:[~2010-11-12  1:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-12  0:15 Recipes updates planned for 1.0 Saul Wold
2010-11-12  1:46 ` Bruce Ashfield [this message]

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=4CDC9C83.7020506@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=sgw@linux.intel.com \
    --cc=yocto@yoctoproject.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.