From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Cleanup / janitors
Date: Tue, 16 Feb 2010 09:18:06 +0000 [thread overview]
Message-ID: <1266311886.6436.108.camel@rex> (raw)
In-Reply-To: <d1b08f941002160108p2e8a880atba367857e3552a22@mail.gmail.com>
On Tue, 2010-02-16 at 10:08 +0100, Andrea Adami wrote:
> > Problem is to do that reliable.
> I would follow RP steps: starting in nov 2009
> http://git.pokylinux.org/cgit.cgi/poky/log/
>
> >It is easy to remove the do_stage section from a recipe, and it is
> >easy to verify that it builds, but it is already becoming less trivial
> >to verify that everything that depends on it builds too, and it
> >becomes complicated if you want to verify that it actually works
> >(especially if you have no clue what the package does).
> That's the reason why I did not dare too
>
> > The other thing that comes to mind is better describing the job. If it
> I'd define it "Monkey-picking from Poky" for the most recipes.
>
> How dangerous could it be? I have no idea about eventual subtle diffs
> between Poky and OE.
The key thing is to make sure the starting recipes were the same. If
they are, the same change probably applies to OE as they are very
similar, I try and keep them roughly in sync in all important ways.
It would actually make sense to add some function which compares the
results of a staging changes, I don't know if anyone would feel up to
that?
Cheers,
Richard
next prev parent reply other threads:[~2010-02-16 9:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 23:38 Cleanup / janitors Chris Larson
2010-02-16 8:13 ` Koen Kooi
2010-02-16 8:39 ` Frans Meulenbroeks
2010-02-16 9:08 ` Andrea Adami
2010-02-16 9:18 ` Richard Purdie [this message]
2010-02-16 9:19 ` Richard Purdie
2010-02-17 15:39 ` contrib tree (was: Cleanup / janitors) Rolf Leggewie
2010-02-16 9:41 ` Cleanup / janitors Koen Kooi
2010-02-16 23:30 ` Tom Rini
2010-02-17 0:57 ` Chris Larson
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=1266311886.6436.108.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.