[oe] cleaning recipes

[Frans Meulenbroeks]

Dear all,

As some of you might have noticed I've been cleaning up our
recipes.during the last week or so.
As I had some time at hand this weekend, lots of cleaning has been done.
I did my very best to stay within the guidelines of the TSC (as
described in http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-May/020047.html),
but it is quite possible that at some point I made a mistake or so.
If so, let me know and I'll repair things and/or revert the commit. (I
feel if you make a mess you should also clean it yourself).

Rationale for doing so is that it makes the tasks as listed in
http://wiki.openembedded.org/index.php/OpenEmbeddedJanitors simpler
(because less recipes need to be looked at).

As it stands the job is not done. I've mainly peeked at all recipes
that had more than 10 versions.

I did not touch core directories like gcc, glibc/uclibc/eglibc,
binutils, although I feel some pruging of old stuff would be useful
there. E.g. is there still a use for gcc 4.1.0 ? )
Then again these are typically well maintained and looked after, so
there are probably hardly any issues that would require cleanup.

I also stayed away from core recipes like linux and u-boot (although I
can imagine some version scould be deprecated. Also the policy on when
to create a different recipe and when to modify an existing one is
vague at best.
Some harmonisation would be nice.

Then there are the opie dirs: bluelightning told me he would look into
this and expire the older versions.

X related stuff was also left untouched JaMa told me he was looking into that.

And I skipped the ti dir. I would propose the ti people look into it.
E.g. is there a need for 12 ti-xdctools recipes, 5 of wihch are pinned
(and yeah, I understand that these probably are closely linked to a
codec engine version, still 12 seems from a process point of view
quite a lot)

Anyway, if there are issues because of this action, or if you feel
removal of a recipe was not in accordance with the TSC guidelines, let
me know and I'll repair.

Have fun!
Frans