From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Package Maintenance
Date: Wed, 25 Mar 2009 17:20:25 +0100 [thread overview]
Message-ID: <gqdlka$cbd$1@ger.gmane.org> (raw)
In-Reply-To: <49CA5638.1050000@dls.net>
On 25-03-09 17:05, Mike (mwester) wrote:
> Koen Kooi wrote:
>> On 25-03-09 09:51, Frans Meulenbroeks wrote:
>>
>>> and a last last thing: about the vetting: not sure whether I fully
>>> understand the idea, but is a lot of this info on what builds on what
>>> not already present in tinderbox?
>>
>> The tinderbox data is purged periodically, so don't depend on it.
>
> In addition, you cannot determine which builds in tinderbox were done
> with an empty TMPDIR -- and unless you have an empty TMPDIR, there's
> really no complete test.
Empty TMPDIR is only once case we should test for, I've seen many times
that a 'populated' TMPDIR creates bugs, e.g. midori picking up libhildon
to mention a recent one. So 'always build from empty TMPDIR' will leave
serious and harder to trackdown bugs unnoticed.
Another example: building qt/e for ppc405 will OOM[1] if you have a
populated TMPDIR, it will work fine from scratch.
We should certainly do builds from scratch to track down dependency and
process bugs, but let's not forget about non-empty TMPDIR bugs.
regards,
Koen
[1] It took me a while to track that one down, since the OOM would
either take sshd down as well, or just lock up the box.
next prev parent reply other threads:[~2009-03-25 16:22 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 19:18 Package Maintenance Chris Larson
2009-03-17 19:25 ` Koen Kooi
2009-03-17 19:32 ` Chris Larson
2009-03-17 19:43 ` Frans Meulenbroeks
2009-03-23 20:35 ` Chris Larson
2009-03-24 9:06 ` Richard Purdie
2009-03-24 15:08 ` Chris Larson
2009-03-24 18:36 ` Frans Meulenbroeks
2009-03-24 18:54 ` Tom Rini
2009-03-24 18:55 ` Chris Larson
2009-03-24 19:14 ` Koen Kooi
2009-03-24 19:24 ` Chris Larson
2009-03-24 19:50 ` Tom Rini
2009-03-24 19:59 ` Chris Larson
2009-03-24 18:56 ` Junqian Gordon Xu
2009-03-24 19:05 ` Chris Larson
2009-03-24 19:19 ` Junqian Gordon Xu
2009-03-24 19:29 ` Philip Balister
2009-03-24 19:51 ` Tim Ellis
2009-03-24 20:01 ` Chris Larson
2009-03-24 20:16 ` Koen Kooi
2009-03-24 20:30 ` Lon Lentz
2009-03-24 20:44 ` Junqian Gordon Xu
2009-03-25 8:51 ` Frans Meulenbroeks
2009-03-25 11:03 ` Koen Kooi
2009-03-25 13:36 ` Richard Purdie
2009-03-25 14:16 ` Holger Schurig
2009-03-25 14:40 ` Richard Purdie
2009-03-25 15:32 ` Holger Schurig
2009-03-25 14:26 ` Otavio Salvador
2009-03-25 16:05 ` Mike (mwester)
2009-03-25 16:20 ` Koen Kooi [this message]
2009-03-25 18:03 ` Jeremy Lainé
2009-03-25 18:22 ` Koen Kooi
2009-03-25 18:13 ` Mike (mwester)
2009-03-25 22:07 ` Frans Meulenbroeks
2009-03-25 22:27 ` Jeremy Lainé
2009-03-25 23:54 ` Mike (mwester)
2009-03-27 9:22 ` Richard Purdie
2009-03-24 19:59 ` Mike (mwester)
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='gqdlka$cbd$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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox