public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rolf Veen <rolf.veen@helide.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Categories
Date: Wed, 04 Jun 2003 16:23:00 +0200	[thread overview]
Message-ID: <3EDE00C4.6060201@helide.com> (raw)
In-Reply-To: <200306031732.48204.george@gentoo.org>

George Shapovalov wrote:
> Ok, this seems to be pretty much it, at least from what I remember
> being mentioned on this topic. Again, if anybody thinks I ommitted
> something, please stand up and mention it :).

Namespace orthogonal to categories.

Categories change, as packages are being added; if a category has more
that N (lets say 50, for example) entries it looses its usefullness.
While browsing for packages it is natural to have some level of depth;
two or tree levels of categories should be ok. Also a package can fit
into more that one category. Let categories be a graph. A symlink
hierarchy, for example.

But since categories are variable and somewhat arbitrary, don't let
the basic system, the core algorithms, depend on them. So take a flat
namespace for packages, resolving name conficts in the download (url
to local dir) phase, adding the necesary information to the ebuild.

Concluding, have a flat namespace for machine interaction, and an
arbitrarily complicated category graph on top of that for user
interaction.

Well, it's an opinion.
Rolf.


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-06-04 14:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-03 18:01 [gentoo-dev] Categories Sebastian Werner
2003-06-04  0:32 ` George Shapovalov
2003-06-04 14:23   ` Rolf Veen [this message]
2003-06-06 16:35     ` Paul de Vrieze
2003-06-09  7:30       ` 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=3EDE00C4.6060201@helide.com \
    --to=rolf.veen@helide.com \
    --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