Richard Purdie wrote:
This is a continuation/summary of a discussion on IRC. It was mentioned
that the NSLU2 people do incremental builds but it would also be nice if
builds from scratch were attempted periodically.
As a user with limited knowledge about OE, I'm convinced we can improve
OE quality. IMHO, periodical install and build from scratch are very
important:
1. for new users so that they can easily get started with OE, without
much installing nor building problems.
This could seem silly to perform periodical install from scratch, but it
is not. Endorsing the end user role and starting from scratch force us
to keep the GettingStarted page up-to-date for end-users.
2. for developers to - as you stated - spot regressions in build.
This implies a rm -rf tmp/
Every two weeks ?
3. for package maintainers because .bb files will be stressed with many
different configuration.
I think we should sometimes - with a lesser period than build though -
clean up the DL-DIR, so that we can ensure that users will not encounter
"no such package" errors; maintainer would also be aware of SRC_URI change.
But Instead of wasting time and bandwidth downloading packages to check
SRC_URIs, maybe we should simply check for SRC_URI validity in all .bb
files with a little script instead :)
4. for all the Open Embedded community because it would enable
developers to provide periodically pre-built distro images.
Do you already use a script to build a distro for multiple machine ? If
yes could you please share it, e.g. through the wiki ?
I think installing and building from scratch periodically should even be
part of the Quality Assurance Architecture
http://oe.handhelds.org/cgi-bin/moin.cgi/QualityAssuranceArchitecture.
I said I'd send a list of combinations that should work which people
could volunteer to test. Ultimately, I'd like to see these run
automatically and have the results collected. We have some
infrastructure in place for this (tinderbox) thanks to Zecke although
I'm not sure how to use it :). The idea would be to spot regressions in
builds more quickly.
I'm volunteer to build the following distributions for Zaurus: angstrom,
openzaurus-unstable.
I have some tinderbox-related question though:
To send build report to Tinderbox, in which file should be all the
TINDER_LOG, TINDER_REPORT, etc. defined ? local.conf ?
Just for info, are build report sent on build failure only ? always sent
whatever the build status ?
What about automatically send build bug report to bugzilla ? Or to
oe.pastebin.com ?
BTW, there is a python script that can be used to upload file or piped
data to pastebin.ca:
http://raphael.slinckx.net/blog/2005-08-31/the-wonders-of-pastebin (i'm
sure pastebin fan will like it :)
Thanks in advance for your answer.
Best regards,
Cyril
_______________________________________________
Oe mailing list
[email protected]
https://www.handhelds.org/mailman/listinfo/oe
