From: Jamie Lenehan <lenehan@twibble.org>
To: openembedded-devel@openembedded.org
Subject: Re: Section list
Date: Tue, 29 Aug 2006 11:18:52 +1000 [thread overview]
Message-ID: <20060829011852.GC31668@twibble.org> (raw)
In-Reply-To: <20060829011415.GA31668@twibble.org>
This time I'll send this to the list...
On Mon, Aug 28, 2006 at 11:47:00AM +0200, Marcin Juszkiewicz wrote:
> Dnia poniedziałek, 28 sierpnia 2006 01:39, Jamie Lenehan napisał:
[...]
> > * console/shells
>
> base/shell and console/shells? I would choose one.
base/shell is the most common, only fush uses console/shells, so make
this one base/shell.
[...]
> > * kernel
> > * kernel/module -> REPALCE with kernel/modules
> > * kernel/modules
>
> virtual/kernel modules -> kernel, out-of-tree modules -> kernel/modules
>
> What do you think?
I don't think that makes much sense. I would go to section "kernel"
to find a new kernel and to "kernel/modules" to find modules for the
kernel. I don't think it matters to the end user where those modules
were from.
[...]
> > * x11/gnome
> > * x11/gnome/libs
>
> How does those two differ from other "gnome" ones? Can we move x11/gnome
> to x11/* and x11/gnome/libs -> x11/libs?
Hmm, yeah there are a few gnomes:
* gnome/libs
* gnome/multimedia
* x11/gnome
* x11/gnome/libs
The gnome core puts itself in x11/gnome/* while apps/libraries from other
people seem to put themselves in gnome/*. So you think this is the best way
to handle this?:
* gnome/libs -> x11/libs
* gnome/multimedia -> x11/multimedia
* x11/gnome -> x11
* x11/gnome/libs -> x11/libs
--
Jamie Lenehan <lenehan@twibble.org>
prev parent reply other threads:[~2006-08-29 1:20 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
2006-08-29 1:18 ` Jamie Lenehan [this message]
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=20060829011852.GC31668@twibble.org \
--to=lenehan@twibble.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox