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: Mon, 09 Jun 2003 09:30:41 +0200	[thread overview]
Message-ID: <3EE437A1.10805@helide.com> (raw)
In-Reply-To: <200306061835.52352.pauldv@gentoo.org>

Paul de Vrieze wrote:

> Unfortunately CVS does not work well with symlinks, so this is not
> really an option. 

Not unavoidable. Let a script and a descriptor combination
reconstruct the whole hierarchy, i.e., ebuild the categories.
Starting from a descriptor in XML (for example), you could ebuild
a symlink hierarchy, or you could choose other backends too, such
as a database (in a distant future).

Or you could even include categories in each ebuild descriptor. Each
package says to which categories it belongs.

> Flat namespaces are actually slower in machine interaction. There are
> allready very many packages in portage currently. Thousands of
> entries in a directory is NOT fun to look at, or to search for a
> computer (albeight doable).

Examples of what I'm proposing are Sourceforge and Freshmeat. Both
use flat namespaces, and on top of that a search engine and a complex
category structure. And they manage a lot of entries ! Sourceforge
solves the directory problem in the form /g/ge/gentoo; that can be
handled transparently by the tools.

Cheers / Groeten.
Rolf.


--
gentoo-dev@gentoo.org mailing list


      reply	other threads:[~2003-06-09  7:33 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
2003-06-06 16:35     ` Paul de Vrieze
2003-06-09  7:30       ` Rolf Veen [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=3EE437A1.10805@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