All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Initial Proposal for Packaged Staging Revamp (was [RFC] Make some big changes right after next stable)
Date: Thu, 04 Mar 2010 10:15:02 +0000	[thread overview]
Message-ID: <1267697702.2259.243.camel@rex> (raw)
In-Reply-To: <hmm5jv$e77$1@dough.gmane.org>

On Wed, 2010-03-03 at 18:17 +0100, Koen Kooi wrote:
> On 03-03-10 18:09, Chris Larson wrote:
> > To summarize, I propose the creation of an archive/package which acts as the
> > primary artifact to come out of the build of a recipe. 
> 
> That sounds like a good way to do packaged-staging without making my
> head explode :)

This is mainly due to the constraints that were placed upon its
development. If we can relax some of the constraints, we can make it
simpler.

> I think the 'private staging' approach is the way to go, it makes the
> build determistic instead of "might pick up extras from staging". And I
> think it will also cure the mysterious "every python recipe breaks when
> some, yet unknown, recipe is built"

Yes, private staging areas are something we need and I don't think
anyone believes otherwise. This isn't something either proposal is
offering directly. Its only something that it will be possible to
develop more easily once we have staging packages working well.

Cheers,

Richard




  reply	other threads:[~2010-03-04 15:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-03 17:09 [RFC] Initial Proposal for Packaged Staging Revamp (was [RFC] Make some big changes right after next stable) Chris Larson
2010-03-03 17:17 ` Koen Kooi
2010-03-04 10:15   ` Richard Purdie [this message]
2010-03-03 17:43 ` Richard Purdie
2010-03-03 18:28   ` Chris Larson
2010-03-03 19:50     ` Frans Meulenbroeks
2010-03-04 10:09     ` Richard Purdie
2010-03-05 15:38 ` Phil Blundell

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=1267697702.2259.243.camel@rex \
    --to=rpurdie@rpsys.net \
    --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.