[oe] testing branch 2010-10-29

[Frans Meulenbroeks]

2010/10/31 Koen Kooi <k.kooi at student.utwente.nl>:
> On 31-10-10 22:03, Yuri Bushmelev wrote:

>> Every build will be started with clean $TMPDIR for now at least
>
> I mentioned this at OEDEM as well, only doing clean builds hides upgrade
> path type of bugs (e.g. libcdio5 -> libcdio). It would be nice if an
> incremental build going from testing-prev to testing-next would be done
> as well before tagging.

>From the wiki page [1], item 2:
"All volunteers start a clean build and build the combinations they
test, update the above chart, and report status/issues as replies to
the above email. "

But as far as I'm concerned feel free to run incremental tests and put
the results on the testing page (indicating that it is from an
incremental build).

I will remain starting with a clean tmp for now. As it stands:
- I don't have the space to store 6 tmp dirs
- There seem to be sufficient issues with a clean build
- My employer (who sponsors my testing activities by donating cpu
cycles and storage) is into embedded systems. Partial upgrades are not
relevant in our kind of embedded systems. A reliable and reproducible
build is much more important to us, hence my focus on clean builds.

Enjoy Frans.

PS: a few comments wrt the libcdio issue:

- it would have been nice if this was discussed with the recipe
maintainer. This is in accordance with our commit policy [2, 4th
block]. I strongly doubt that this has happened (and apologies if this
is a faulty assumption).
- I have strong doubts that the dependency change is sound. Actually
libcdio and libcddb are in a catch22 situation where both depend on
each other for some sample programs.
Solution is probably to make an additional package for the sample
progs (I seem to recall that is also the way debian handles this).
Haven't had time to dig into this and fix it.
- maybe some of the confusion and issues wrt libs is because the way
to do this is not really well documented. Eric had some questions on
this on irc on this yesterday too.
If you feel there is documentation, please pass a pointer, otherwise
please add some info to the wiki so the problem can be avoided.
(give a man a fish and he can eat a day, learn a man how to fish and
he can eat all his life).
I would have added the info to the wiki or manual myself, but I feel
my understanding of the issue and the way to handle it is not good
enough to be able to write a good section on it.

(btw: a good place would probably be [3] and yeah, I am aware of the
debian renaming [4], but I am also aware of [5] which as an example
says:
FILES_${PN} = "\
    ${bindir}/* \
    ${sbindir}/* \
    ${libexecdir}/* \
    ${libdir}/lib*.so.* \
    .....
which was exactly what was in the original commit [6]:
+FILES_${PN} = "${libdir}/lib${PN}${SOLIB}"
)

[1] http://wiki.openembedded.net/index.php/Testing#Testing_Procedure
[2] http://wiki.openembedded.net/index.php/Commit_Policy
[3] http://docs.openembedded.org/usermanual/usermanual.html#recipes_examples
[4] http://docs.openembedded.org/usermanual/usermanual.html#id593730
[5] http://docs.openembedded.org/usermanual/usermanual.html#id593138
[6] http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=b672b28ba6a29e2715c91fcbbda8b2776b6f1105