public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Georgi Georgiev <chutz@gg3.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] namespace and categories ( was: Media-music category)
Date: Tue, 3 Jun 2003 01:27:36 +0900	[thread overview]
Message-ID: <20030602162736.GA14984%chutz@gg3.net> (raw)
In-Reply-To: <1054569924.19464.7.camel@phaze>

On 02/06/2003 at 12:05:24(-0400), Todd Berman used 1.4Kbytes just to say:
> > I would separate namespace and categories: let portage work with a
> > *flat* namespace that does not depend on categorization. A package may
> > well fit in more than one category, as you say.
> As far as I know, portage does work on a flat namespace, well, relatively flat at least :)
> > I find categorization too arbitrary to include in a robust tool like
> > portage. So, give the users a 'category view' on top a flat namespace,
> > but use these categories only for information. In fact, categories can
> > be made of only a hierarchy of symlinks to the main directory:
> > 
> > ¿ Too much files in the main directory then ? That's is a different
> > problem. But not one that justifies, on its own, the use of categories.
> >
> > Rolf
> > 
> > (My first post here: hi all)
> 
> wrt to the rest of that, I am actually in favor of MORE categorization.
> I think instead of having dev-this, dev-that, etc, it should be dev/this
> and dev/that.

Greatness!

It was about time we got to that conclusion. A tree-like category view is what
portage needs. I add my vote in support for that. It seems lots of packages
would have to be renamed though - app-emacs/vm -> vm-emacs, app-xemacs/ispell
-> ispell-xemacs etc.

-- 
 /^^^^^^^^^^^^^^^^^^^^^^^^^^^\/^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\
/ Georgi Georgiev    (-<     / Given its constituency, the only \
\ chutz@chubaka.net  /\   .o)\ thing I expect to be "open"      /
/ +81(90)6266-1163  V_/_ |(/)/ about [the Open Software         \
\                   ^^^^^^^^^\ Foundation] is its mouth. --     /
 \                           / John Gilmore                     \
  \_________________________/\__________________________________/

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-06-02 16:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-02 10:19 [gentoo-dev] Media-music category Jon Ellis
2003-06-02 10:58 ` Georgi Georgiev
2003-06-02 12:28   ` rob holland
2003-06-02 11:46 ` Ian Phillips
2003-06-02 12:55   ` rob holland
2003-06-02 12:17     ` Georgi Georgiev
2003-06-02 12:37       ` Troy Dack
2003-06-02 12:58         ` Jon Ellis
2003-06-02 13:24           ` Georgi Georgiev
2003-06-02 15:11             ` rob holland
2003-06-02 15:36               ` Todd Berman
2003-06-02 16:28                 ` rob holland
2003-06-02 15:43                   ` Todd Berman
2003-06-02 16:01             ` [gentoo-dev] namespace and categories ( was: Media-music category) Rolf Veen
2003-06-02 16:05               ` Todd Berman
2003-06-02 16:27                 ` Georgi Georgiev [this message]
2003-06-02 16:46                 ` Rolf Veen

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=20030602162736.GA14984%chutz@gg3.net \
    --to=chutz@gg3.net \
    --cc=chutz-dated-1055780857.27106d@gg3.net \
    --cc=gentoo-dev@gentoo.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