All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lenehan <lenehan@twibble.org>
To: Paul Sokolovsky <pmiscml@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: Section list
Date: Mon, 11 Sep 2006 09:11:59 +1000	[thread overview]
Message-ID: <20060910231158.GA9915@twibble.org> (raw)
In-Reply-To: <597749586.20060909152031@gmail.com>

On Sat, Sep 09, 2006 at 03:20:31PM +0300, Paul Sokolovsky wrote:
[...]
> 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.

I've changed in the documentation just now to note that it's a
recomendation only and that new additions/changes should be be
discussed cia OE mailing list.

The list was actually done by myself when trying to decide what
sections to put stuff in. I generated the list from the existing OE
packages and then noticed various things such as the use of "net" and
"networking" and the like. So the list is really just what was there
with some of these things removed, plus a few other changes from
other peoples comments.

So I think it's useful to have a documented list... the document can
always be changed!

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

Only two ;) I went round and round on dozens of them before sending
out my original list!

>   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?

That's definitely a question I had as well. Do you care if an
application is a gnome app, or a kde app or a motif app? Or do you
just want an "X app" that does what you want? I checked a few distros
and then didn't appear to distinguish between gnome/kde/motif etc. On
the other hand maybe we do care in OE since installing a gnome app
may pull in a huge number of gnome libraries?

[...]
>   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.

That sound fine. I don't think you can make things worse by fixing up
the current section lists ;) And if you think other things you want
changed in the list please do send an email - preferably with a
propsed change (since finding a good solution is usually the most
difficult part!)

Thanks.

-- 
 Jamie Lenehan <lenehan@twibble.org>



  reply	other threads:[~2006-09-10 23:15 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
2006-09-10 23:11             ` Jamie Lenehan [this message]
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=20060910231158.GA9915@twibble.org \
    --to=lenehan@twibble.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=pmiscml@gmail.com \
    /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.