public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jean Jordaan <jean@upfrontsystems.co.za>
To: Grant Goodyear <g2boojum@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-core] Breaking up the beast known as app-games
Date: Fri, 05 Sep 2003 10:19:25 +0200	[thread overview]
Message-ID: <3F58470D.4050304@upfrontsystems.co.za> (raw)
In-Reply-To: <1062713398.25562.112.camel@localhost>

>>Both make sense, and app-editors/yudit & app-editors/yudit would
>>also make sense. Instead of categories, ebuilds should have a
>>CATEGORY variable. E.g.
> 
> Portage support would be required to support deeper trees.  

Note that I'm not talking about trees at all. I'm talking about
a flat list of ebuilds, where every ebuild belongs to several
categories of different levels of specificity.

> The problem
> with symlinks is that we use CVS for our portage tree, 

I don't propose any symlinking.

> I, too, would like to see support for a more heirarchical portage tree
> in a future version of portage.

I think a hierarchy, where every ebuild has a specific place in
the tree, is a bad fit for portage or for any packaging system.
One does need a taxonomy or controlled list of categories, but
an ebuild can legitimately belong to many categories.

As drobbins says, though, current portage code is tied to the
category structure. Which is perfectly workable, really :)  I
just completely ignore the category, and use `emerge search` to
find packages. It only bugs developers who have to decide &
revise in which category to put a package. However, I'd like
categories to become more useful for me as user.

-- 
Jean Jordaan
http://www.upfrontsystems.co.za


--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-09-05  8:19 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-04 16:51 [gentoo-dev] Breaking up the beast known as app-games Mike Frysinger
2003-09-04 17:59 ` [gentoo-dev] Re: [gentoo-core] " Donny Davies
2003-09-04 18:07   ` Camille Huot
2003-09-04 19:02     ` Mike Frysinger
2003-09-04 19:45       ` Camille Huot
2003-09-04 20:14         ` Thomas de Grenier de Latour
2003-09-05  4:13           ` Mike Frysinger
2003-09-05  6:52             ` Thomas de Grenier de Latour
2003-09-05  8:15           ` Philippe Lafoucrière
2003-09-05 18:39             ` Thomas de Grenier de Latour
2003-09-06  0:17               ` Luke-Jr
2003-09-06  1:04                 ` Mike Frysinger
2003-09-06  1:50                 ` Thomas de Grenier de Latour
2003-09-06  2:03                   ` Luke-Jr
2003-09-06  3:27                     ` Robin H. Johnson
2003-09-06  4:18                       ` Luke-Jr
2003-09-06  7:47                         ` George Shapovalov
2003-09-06 13:38                           ` Luke-Jr
2003-09-06 15:35                             ` Martin Schlemmer
2003-09-07  0:06                               ` Luke-Jr
2003-09-07  1:12                                 ` Martin Schlemmer
2003-09-06  8:48               ` Philippe Lafoucrière
2003-09-04 19:14     ` Luke-Jr
2003-09-04 19:42       ` Camille Huot
2003-09-04 19:45         ` Luke-Jr
2003-09-04 20:47     ` George Shapovalov
2003-09-04 20:52       ` Jean Jordaan
2003-09-04 22:09         ` Grant Goodyear
2003-09-04 22:26           ` Luke-Jr
2003-09-05  8:19           ` Jean Jordaan [this message]
2003-09-04 23:41       ` Daniel Robbins
2003-09-04 22:14     ` Jan Krueger
2003-09-05  8:22 ` [gentoo-dev] " Philippe Lafoucrière
2003-09-05  8:51   ` Ralph F. De Witt
2003-09-05 12:29     ` Mike Frysinger

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=3F58470D.4050304@upfrontsystems.co.za \
    --to=jean@upfrontsystems.co.za \
    --cc=g2boojum@gentoo.org \
    --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