All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Tom Rini <tom.rini@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Moving angstrom under the yocto banner
Date: Tue, 03 Apr 2012 10:07:24 -0700	[thread overview]
Message-ID: <4F7B2E4C.5030408@linux.intel.com> (raw)
In-Reply-To: <20120403164043.GE4816@bill-the-cat>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On 04/03/2012 09:40 AM, Tom Rini wrote:
> On Tue, Apr 03, 2012 at 09:32:27AM -0700, Darren Hart wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> 
>> On 04/03/2012 09:25 AM, Martin Jansa wrote:
>>> On Tue, Apr 03, 2012 at 09:01:01AM -0700, Darren Hart wrote:
>>>> -----BEGIN PGP SIGNED MESSAGE----- Clear reproducible
>>>> testing results. Whether or not a pair of git clones and some
>>>> tinkering can result in the same thing as a poky repository
>>>> or not isn't relevant in my opinion. I believe that we need a
>>>> consistent mode of validating support for a Yocto Project X.Y
>>>> release. Now if that is accomplished by building with the
>>>> poky repository of the same vintage or by running some script
>>>> that pulls the right bits together independently.... I
>>>> honestly don't care, but I do think it should be consistent.
>>> 
>>> so teach setup script something like: poky.sh checkout X.Y
>>> (which checkouts whatever parts are needed for X.Y) poky.sh
>>> update X.Y (dtto)
>>> 
>>> Which creates the same structure like poky repository has, but
>>> by checkouting upstream repositories or using submodules or
>>> whatever.
>>> 
>>> That's what oebb.sh and SHR makefile does for master/shr HEADs,
>>> but can be extended do it for particular version too.
>> 
>> 
>> This is certainly doable, but it doesn't address the
>> stabilization buffer poky provides that I mentioned.
> 
> While I want to reply to your whole email, I want to ask now, is
> there really a stabilization buffer being provided?  I could see
> that being the case if we were talking about depending on something
> independent of this effort (gcc, eglibc, make) but we're talking
> about oe-core and bitbake.  The folks in charge of poky the repo
> are in charge of oe-core and bitbake.  There might be an
> unintentional lag between when Richard can push changes to poky the
> repo, but I don't think it's great (and hey, freeing up Richard's
> time for other stuff is probably a good thing :)).
> 

I believe there is. It's a small temporal buffer though. I'd be
interested in RP's thoughts here.

- -- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPey5MAAoJEKbMaAwKp364g7oH/RJxQqfOJpCdIz4qaC81hQWt
u0SUBpqS4FEUMT5JCgxRztaKsq8+irFTYUODvEDzVTDY8hJJ7rd+QKKnYlgSFT1o
vB9qerea1fQZMEAw0J1CmXRCD9tuBN7nMec6Z36KIcJXp0KrAZrSMzgF20byeGTf
YjusfkiNOIdVt3q1AtESlQbbAzmiFlvlGxSn4v8hLtXzL36XGyQ//1Lg1mr1ZXvm
rqEgN3bA4CdI/tgg6AMjOAI0KnXKj2tWn7o4Gule9pcRycg18XdE+iGZGmSxDdGM
+4gE54rwQlrM/2cMM3n0qhzqAyB4o8vnsvPBQyt+DXCy6ErAaqnP25Y31rW7EvY=
=MpXf
-----END PGP SIGNATURE-----


  reply	other threads:[~2012-04-03 17:08 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-30 18:44 Moving angstrom under the yocto banner Koen Kooi
2012-03-30 19:00 ` Osier-mixon, Jeffrey
2012-04-10 14:04   ` Koen Kooi
2012-04-10 16:07     ` Stewart, David C
2012-03-30 19:26 ` Mark Hatle
2012-03-30 19:33   ` Koen Kooi
2012-03-30 20:18     ` Mark Hatle
2012-03-30 20:33       ` Koen Kooi
2012-03-30 20:45       ` Tom Rini
2012-03-30 20:51         ` Koen Kooi
2012-03-30 20:55           ` Osier-mixon, Jeffrey
2012-03-30 21:02         ` Eric Bénard
2012-03-30 21:01       ` Osier-mixon, Jeffrey
2012-03-30 21:12         ` Koen Kooi
2012-03-30 21:11       ` Richard Purdie
2012-03-30 23:06         ` Stewart, David C
2012-03-30 23:09           ` Chris Larson
2012-03-30 23:14             ` Tom Rini
2012-03-30 23:49           ` Tom Rini
2012-03-30 23:58             ` Koen Kooi
2012-03-30 23:52         ` Darren Hart
2012-03-31  0:08           ` Koen Kooi
2012-03-31  0:28             ` Darren Hart
2012-03-31  0:53               ` Koen Kooi
2012-03-31  1:21                 ` Darren Hart
2012-03-31  1:37                   ` Koen Kooi
2012-03-31  2:27                     ` Darren Hart
2012-03-31  3:00                       ` Chris Larson
2012-03-31  3:27                         ` Darren Hart
2012-03-31  7:06                         ` Richard Purdie
2012-03-31 10:00                           ` Frans Meulenbroeks
2012-04-02  4:08                           ` Matthew McClintock
2012-04-02 11:27                             ` Richard Purdie
2012-04-02 17:13                       ` Tom Rini
2012-04-03 16:01                         ` Darren Hart
2012-04-03 16:25                           ` Martin Jansa
2012-04-03 16:32                             ` Darren Hart
2012-04-03 16:40                               ` Tom Rini
2012-04-03 17:07                                 ` Darren Hart [this message]
2012-04-03 16:44                               ` Martin Jansa
2012-04-03 17:08                                 ` Darren Hart
2012-04-03 17:15                                   ` Tom Rini
2012-04-03 17:26                                     ` Chris Larson
2012-04-03 17:34                                       ` Brian Hutchinson
2012-04-03 18:03                                         ` Darren Hart
2012-03-31 16:30         ` Khem Raj
2012-04-01  0:51           ` Chris Larson
2012-03-31 15:37 ` Paul Eggleton
  -- strict thread matches above, loose matches on Subject: below --
2012-03-30 22:32 Daniel Lazzari

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=4F7B2E4C.5030408@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=tom.rini@gmail.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.