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 14:13:59 -0400 [thread overview]
Message-ID: <1117995239.17948.21.camel@localhost> (raw)
In-Reply-To: <42A3358B.20802@ieee.org>
On Sun, 2005-06-05 at 13:25 -0400, Nathan L. Adams wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> foser wrote:
> > On Sun, 2005-06-05 at 18:34 +0200, Jonas Geiregat wrote:
> >
> >>I do agree with you but some package just have completely wrong place
> >>within portage, such package placements migh confuse the user.
> >>To give an example: mzscheme was placed in dev-lisp while portage had a
> >>dev-scheme directory.
> >
> > The current set-up isn't user-browseable anyway and hasn't been for a
> > long time. I don't think the focus should be on correcting that in the
> > tree, the user tools should be improved really.
> >
>
> Then why is their a browsable "Categories" link on the packages site?
>
> http://packages.gentoo.org/categories/
>
> I don't agree with Ned. Organizing the packages logically makes things
> less confusing for the end-user and developers alike and doesn't qualify
> as a "cosmetic reason". It *is* valuable work, IMHO.
And how long before somebody proposes sys-auth?
*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.
--
Ned Ludd <solar@gentoo.org>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-06-05 19:03 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 [this message]
2005-06-05 20:57 ` Nathan L. Adams
2005-06-05 21:03 ` Nathan L. Adams
2005-06-05 21:55 ` Ned Ludd
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=1117995239.17948.21.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