public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ned Ludd <solar@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal: sys-pam category
Date: Sun, 05 Jun 2005 17:55:22 -0400	[thread overview]
Message-ID: <1118008522.2711.30.camel@localhost> (raw)
In-Reply-To: <42A3672F.1090304@ieee.org>

On Sun, 2005-06-05 at 16:57 -0400, Nathan L. Adams wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Ned Ludd wrote:
> > *poof* we now reshuffle, but then we can do auth with ldap. So lets
> > move 
> > all the */ldap* related subjects under it sys-auth/... Then a month or 
> > six later comes along sys-ldap and it gets moved there. The logic will 
> > go full circle before long if we consistently keep shuffling packages
> > around.
> > 
> > All in all this is seriously the reason why ebuilds have a DESCRIPTION= 
> > and one of the reasons we have metadata.xml files.
> >
> 


> Well obviously there needs to be a consensus on *how* to logically
> organize things before anyone goes willy nilly changing stuff. Do you
> group by what the package is used for (email vs. game vs. web browser)
> or by what it is built from (PERL stuff, Gnome apps, KDE apps). It
> appears that currently its a mix. Is that documented anywhere?

You raise a good point and sadly that is the unfortunate thing here.. 
There is no clear consensus right now and we have yet to really have a 
fruitful thread on the subject. I not aware of any intelligent 
documentation on this subject either.

> I personally think the organization should be from an end-user
> perspective as much as possible. Imagine for a moment that you are a
> Genewbie (new Gentoo user). You have a new minimal installation and you
> want to add some applications. How do you know what your choices are for
> an email client, for instance? You could find most things here:


> Again, I think better
> organization and improved tools are both worth while.

I fully agree with you on improved tools and would rather see us go 
this route before we end up with >300 top level categories.

-- 
Ned Ludd <solar@gentoo.org>

-- 
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2005-06-05 21:57 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-05 14:22 [gentoo-dev] Proposal: sys-pam category Diego 'Flameeyes' Pettenò
2005-06-05 14:44 ` Alin Nastac
2005-06-06  0:34   ` Mike Doty
2005-06-06  4:00     ` Alin Nastac
2005-06-05 15:37 ` Ned Ludd
2005-06-05 16:34   ` Jonas Geiregat
2005-06-05 16:42     ` foser
2005-06-05 17:25       ` Nathan L. Adams
2005-06-05 18:13         ` Ned Ludd
2005-06-05 20:57           ` Nathan L. Adams
2005-06-05 21:03             ` Nathan L. Adams
2005-06-05 21:55             ` Ned Ludd [this message]
2005-06-06 10:43               ` Jan Jitse Venselaar
2005-06-05 19:13         ` Jonas Geiregat
2005-06-05 17:34   ` Diego 'Flameeyes' Pettenò
2005-06-05 19:03     ` Ned Ludd
2005-06-05 19:21       ` Diego 'Flameeyes' Pettenò
2005-06-05 20:13         ` Ned Ludd
2005-06-06 19:47         ` Kevin F. Quinn
2005-06-05 17:50   ` Michael Cummings
2005-06-05 18:10     ` Lance Albertson
2005-06-06 14:06     ` [gentoo-dev] " sf
2005-06-06 14:29       ` Jason Stubbs
2005-06-05 15:59 ` [gentoo-dev] " Ian Leitch
2005-06-05 22:03 ` Robin H. Johnson

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=1118008522.2711.30.camel@localhost \
    --to=solar@gentoo.org \
    --cc=gentoo-dev@lists.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