All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: OE breakages, was: Re: fakeroot fails to build
Date: Wed, 25 Feb 2009 16:43:21 +0100	[thread overview]
Message-ID: <go3oup$b6r$1@ger.gmane.org> (raw)
In-Reply-To: <49A5606D.3050507@dls.net>

On 25-02-09 16:14, Mike (mwester) wrote:

> ((Also, are there any non-angstrom distros still left in OE, besides
> SlugOS?  I really feel like I'm swimming upstream all the time with OE
> -- things break for me so often that just don't seem to affect anyone
> else...))

Things break often<period>

I'm 'fortunate' enough to be able to spend 2 hours every day fixing 
breakages for angstrom, so I can get a working demo for my presentation 
at the bossaconference. Thanks to all the people in the beagleboard 
community I get notified of breakages pretty much the instant they 
happen, which makes finding the cause a lot easier.

This also means that my 'OE time' is almost completely filled with 
bugfixing, instead of working that is fun. I've been trying to push for 
better testing frameworks and removing the taboo stamp from the word 
'review'.

The review bit seems to gaining traction, but 'testing' is still a alien 
and mystic concepts for a lot of OE committers. Worse, some people turn 
*off* testing frameworks like insane.bbclass!

Maybe it's time for OE to consider whether it really wants a zillion 
commits per day or only a few tested commits per day. Having a ton of 
active developers means nothing when people using OE can never get a 
build completed due to all the small, but fatal bugs appearing lately.

I'm close to finishing the new stable branch manifesto which lists 
options and procedures to make it easier to do releases of OE (not 
builds, releases of the metadata itself) and track regressions, but it 
would need about 3 or four people spending a few hours on it every week, 
which sadly might not be feasible, since the .dev branch is too nice and 
shiny compared to any branch.

regards,

Koen





  reply	other threads:[~2009-02-25 15:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-25  6:53 fakeroot fails to build Mike (mwester)
2009-02-25  7:57 ` Koen Kooi
2009-02-25  8:23   ` Michael 'Mickey' Lauer
2009-02-25 15:04     ` Koen Kooi
2009-02-25 15:14     ` Mike (mwester)
2009-02-25 15:43       ` Koen Kooi [this message]
2009-02-26 13:05         ` OE breakages, was: " Bernhard Guillon
2009-02-27 19:30           ` Rodrigo Vivi
2009-02-25 18:25       ` Minimal distro (was: fakeroot fails to build) Michael 'Mickey' Lauer
2009-02-25 18:59         ` Tom Rini
2009-02-25  8:06 ` fakeroot fails to build Michael 'Mickey' Lauer
  -- strict thread matches above, loose matches on Subject: below --
2009-02-26 17:20 OE breakages, was: " Frans Meulenbroeks
2009-02-26 19:37 ` Michael 'Mickey' Lauer
2009-02-27 16:06 ` Leon Woestenberg
2009-02-27 16:26   ` Tom Rini
2009-02-27 17:56     ` Frans Meulenbroeks
2009-02-27 19:35       ` Tom Rini
2009-02-28 10:54     ` Frans Meulenbroeks
2009-02-28 15:53       ` Tom Rini
2009-02-28 18:07         ` Frans Meulenbroeks
2009-02-28 18:29           ` Tom Rini
2009-03-01 17:09             ` Koen Kooi
2009-03-02 18:55               ` Tom Rini

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='go3oup$b6r$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.