[oe] Section list

[Paul Sokolovsky]

Hello Koen,

Saturday, September 9, 2006, 12:46:05 PM, you wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1

> Jamie Lenehan schreef:
>> Updated list, including your changes:

> <list>

> Don't forget to mention that you added it do the usermanual:
> http://www.openembedded.org/user-manual&dpage=ch07s09 :)


  ... And I just wanted to write that it would be nice to add the
proposed list to http://www.openembedded.org/wiki/Policies . Maybe
it's better to let it stay for some time as RFC before adding to
the documentation? Organizing a good taxonomy is not an easy task,
would need some testing on existing package base, and even after that,
it's probably good idea to be prepared to refactors of it.

  Last week, I myself went thru few recipes to add/tweak SECTIONs for
them, and there already were few questions.

  One good example, is that ignorant user part of me is a bit
concerned with x11 section being so broard, with an SDL game, ye olde
MOTIF app and contemporary GNOME/GTK+ app would go into it. That
loses a bit deal of descreptivism. I know, that such taxonomy is
(wonder if there will be chance to say "was") pretty common, and I'm
afraid I don't have elegant proposal for split up. But my ignorant
user part, not concerned with formal correctness, but rather
with pragmatic convenience, says, that there might be possible to have
a "gnome" section (warning: do not mix with GNOME/Gnome ;-) ) for apps
written using contemporary GUI toolkit, like (and mostly) GTK+.

  So, is there any rational idea in that or should my ignorant user
part just shut up?


  Either way, as mood permits, I'm going to continue monkey's job of
applying SECTIONs, based on the list proposed. Just in case, I in
advance apoligize if my selections won't be every time 100% perfect -
as I told, we just should accept this as an iterative process. The
initial aim would be to offload default "base" section off stuff which
easily can be put elsewhere.

> regards,

> Koen


-- 
Best regards,
 Paul                            mailto:pmiscml at gmail.com