All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OE recipe tree quality
Date: Sun, 01 Aug 2010 19:48:44 +0100	[thread overview]
Message-ID: <1280688524.1297.105.camel@rex> (raw)
In-Reply-To: <4C557F47.2080901@balister.org>

On Sun, 2010-08-01 at 10:05 -0400, Philip Balister wrote:
> On 07/31/2010 07:12 PM, Richard Purdie wrote:
> > On Fri, 2010-07-30 at 10:34 +0200, Frans Meulenbroeks wrote:
> >> 2010/7/30 Koen Kooi<k.kooi@student.utwente.nl>
> >>> On 30-07-10 09:21, Esben Haabendal wrote:
> >>>> On Thu, Jul 29, 2010 at 2:07 PM, Philip Balister<philip@balister.org>
> >>> wrote:
> >>>>> On 07/29/2010 05:45 AM, Koen Kooi wrote:
> >
> >>>>>> I would actually advocate removing the 'world' feature from bitbake/OE
> >>>>>> to stop people from wasting time on looking at bitbake world and have
> >>>>>> them fix actual problems.
> >>>>>
> >>>>> bitbake world seems to be the source of pointless listserv discussions.
> >>> Does
> >>>>> it serve any purpose?
> >>>>
> >>>> Pointless or not really depends on how you look at quality.
> >>>>
> >>>> If you look at it as you, Koen and other OE long-timers, yes, it looks
> >>>> rather pointless to have bitbake world.
> >>>> But for those of us who have a different view on what quality is, then
> >>>> bitbake world serves a purpose.
> >>>
> >>> As Thomas points out, as soon as you start blacklisting things (which
> >>> actually increases quality), bitbake world doesn't work anymore.
> >>
> >> Blacklisting does *NOT* increase quality. It just hides the problem and as
> >> such it is ostrich behaviour.
> >>
> >> Instead of masking the problem, better fix things. That is what improves
> >> quality!
> >>
> >> For me a non building recipe is a sign of poor quality.
> >>
> >> BTW: to avoid the blacklisting issue, I've restarted my test with minimal
> >> distro.
> >> Results will probably be available after the weekend.
> >
> > "world" is used by Poky quite successfully. In Poky we expect everything
> > to build with a known list of things that don't. Our aim is to have that
> > list consisting of zero items and I intend to see that happens :).
> 
> But Poky operates under different conditions than the main OE meta-data. 
> Since you more focus on what Poky builds, you do not need to support the 
> variety of recipes in the OE meta-data.

Totally. I was mainly responding to the "world is useless, we should
remove it" comment and also showing that blacklists are used by others
too, in general with success.

Cheers,

Richard






      reply	other threads:[~2010-08-01 18:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-29  8:50 OE recipe tree quality Frans Meulenbroeks
2010-07-29  9:42 ` Thomas Zimmermann
2010-07-29  9:45 ` Koen Kooi
2010-07-29 10:32   ` Frans Meulenbroeks
2010-07-29 12:07   ` Philip Balister
2010-07-29 12:15     ` Frans Meulenbroeks
2010-07-30  7:21     ` Esben Haabendal
2010-07-30  8:22       ` Koen Kooi
2010-07-30  8:31         ` Graeme Gregory
2010-07-30  8:48           ` Frans Meulenbroeks
2010-07-30  8:56             ` Graeme Gregory
2010-07-30  9:07               ` Frans Meulenbroeks
2010-07-30  9:09                 ` Graeme Gregory
2010-07-30  9:36                 ` Marcin Juszkiewicz
2010-07-30  8:54           ` Esben Haabendal
2010-07-30  8:34         ` Frans Meulenbroeks
2010-07-30  8:41           ` Koen Kooi
2010-07-30  9:01             ` Frans Meulenbroeks
2010-07-30 15:39               ` Dr. Michael Lauer
2010-07-31 23:12           ` Richard Purdie
2010-08-01  5:10             ` Frans Meulenbroeks
2010-08-01 14:05             ` Philip Balister
2010-08-01 18:48               ` Richard Purdie [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=1280688524.1297.105.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.