public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal: sys-pam category
Date: Sun, 5 Jun 2005 21:21:37 +0200	[thread overview]
Message-ID: <200506052121.38746@enterprise.flameeyes.is-a-geek.org> (raw)
In-Reply-To: <1117998205.5746.2.camel@localhost>

[-- Attachment #1: Type: text/plain, Size: 1568 bytes --]

On Sunday 05 June 2005 21:03, Ned Ludd wrote:
> 14 files matching the pam prefix and 18 thing matching description.
You missed pam_ssh. And that's just an example.
By the way... mind telling everyone here how did you do that search? I still 
feel that looking for pam things in a *single* place is more useful than 
looking in many different places.

If you feel that sys-auth is more logical, seems good to me. I haven't said 
that it *must* be sys-pam.. was a proposal and as proposal is something I'd 
like to discuss.

> If you really feel you must invalidate everybody else binary trees
> and adding a workload on others for your gain then go for it.
For my gain? Wait I was talking of me in this case but it's not just me.
I think everyone which is looking for pam modules would like to search 
something like sys-pam, instead of looking here and there on the tree or 
trying to use some strange black-magic queries.
By the way, if you're looking for pam modules, your results are quite full of 
cruft.

> But adding another category for what are clearly mostly system
> libraries does not make sense me in this case.
Currently sys-libs contains a very wide range of things, just a couple of them 
seems to be strictly related. As I said, if you feel sys-auth is better, 
good. That would probably take also other things like courier-authlib for 
example.
But sys-libs doesn't seem the right place for me.

-- 
Diego "Flameeyes" Pettenò
Gentoo Developer (Gentoo/FreeBSD, Video, Gentoo/AMD64)

http://dev.gentoo.org/~flameeyes/


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-06-05 19:26 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
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ò [this message]
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=200506052121.38746@enterprise.flameeyes.is-a-geek.org \
    --to=flameeyes@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