All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: Koen Kooi <koen@dominion.kabel.utwente.nl>,
	 Jamie Lenehan <lenehan@twibble.org>
Cc: Using the OpenEmbedded metadata to build Linux Distributions
	<openembedded-devel@lists.openembedded.org>
Subject: Re: Section list
Date: Sat, 9 Sep 2006 15:20:31 +0300	[thread overview]
Message-ID: <597749586.20060909152031@gmail.com> (raw)
In-Reply-To: <45028D5D.4020906@dominion.kabel.utwente.nl>

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@gmail.com




  reply	other threads:[~2006-09-09 12:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1GGZOX-0002WU-1s@linuxtogo.org>
2006-08-27 23:39 ` Section list Jamie Lenehan
2006-08-28  9:47   ` Marcin Juszkiewicz
     [not found]     ` <20060829011415.GA31668@twibble.org>
2006-08-29  1:18       ` Jamie Lenehan
2006-09-09  9:46         ` Koen Kooi
2006-09-09 12:20           ` Paul Sokolovsky [this message]
2006-09-10 23:11             ` Jamie Lenehan
2006-08-29  1:18       ` Jamie Lenehan

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=597749586.20060909152031@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=koen@dominion.kabel.utwente.nl \
    --cc=lenehan@twibble.org \
    --cc=openembedded-devel@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.