public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Aron Griffis <agriffis@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Mozilla: Firebird-bin & Firebird-cvs
Date: Wed, 28 May 2003 23:22:15 -0400	[thread overview]
Message-ID: <20030529032215.GA13180@time> (raw)
In-Reply-To: <87vfvuvl3x.fsf@killr.ath.cx>

Matthew Kennedy wrote:[Wed May 28 2003, 05:04:34PM EDT]
> But wait!  Thats what categories are for -- ie. defining some
> namespace. Thus there's no need, and this more or less backs up my
> argument that the category name + package name forms a "fully resolved
> and unique" symbol for emerge to act upon.

Actually, that's a misconception of the purpose of categories in
portage.  It's never been to provide namespaces; that is a side-effect.
Categories make it easier for users to find what packages are available
for a given type of task.  That's their purpose. 

There was a discussion a while ago (um, a couple years ago) about
removing categories completely and having a flat list of packages.  The
argument against this was that the categories provide an easy way for
users (and developers) to see what is available in a given area.  It was
not intended for categories to provide namespaces.

Aron

--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-05-29  3:22 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-19  1:14 [gentoo-dev] Mozilla: Firebird-bin & Firebird-cvs Dhruba Bandopadhyay
2003-05-19  4:54 ` Russell Tennant
2003-05-19  5:38   ` Chris PeBenito
2003-05-19  9:56     ` Alastair 'liquidx' Tse
2003-05-19 11:01       ` Georgi Georgiev
2003-05-19 13:22         ` Alastair 'liquidx' Tse
2003-05-19 18:52   ` Martin Schlemmer
2003-05-19  6:40 ` Spundun Bhatt
2003-05-19  9:49 ` Christian Gut
2003-05-25 12:43 ` Christian Axelsson
2003-05-25 12:46   ` Dhruba Bandopadhyay
2003-05-25 12:56     ` Christian Axelsson
2003-05-25 13:16       ` Georgi Georgiev
2003-05-25 17:26         ` Zack Gilburd
2003-05-25 18:31     ` Jon Portnoy
2003-05-28  8:22   ` Matthew Kennedy
2003-05-28  8:47     ` Kumba
2003-05-28  9:06       ` Georgi Georgiev
2003-05-28  9:20         ` Kumba
2003-05-28  9:54           ` Michael Kohl
2003-05-28 14:06         ` Jon Portnoy
2003-05-28 18:13           ` George Shapovalov
2003-05-28 19:08             ` Jon Portnoy
2003-05-28 21:04               ` Matthew Kennedy
2003-05-28 21:14                 ` Dave Nellans
2003-05-28 22:40                   ` George Shapovalov
2003-05-29  3:22                 ` Aron Griffis [this message]
2003-05-29  6:40                   ` John Robinson
2003-05-29 10:17                     ` Matt Tucker
2003-05-29 13:31                       ` John Robinson
2003-05-29 14:00                         ` Tavis Ormandy
2003-05-29 14:27                           ` John Robinson
2003-05-30  7:03                   ` Matthew Kennedy
2003-05-30  7:15                     ` Georgi Georgiev
2003-05-30 10:52                     ` Christian Axelsson
2003-05-30 15:23                     ` Grant Goodyear
2003-06-15 11:28                 ` Matthew Kennedy
2003-05-28 19:21             ` Jon Portnoy
2003-05-29  3:24               ` Aron Griffis
2003-05-30  6:45                 ` Matthew Kennedy
2003-05-28 23:56             ` William F Pearson III
2003-05-28  9:08     ` Troy Dack

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=20030529032215.GA13180@time \
    --to=agriffis@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