From: flameeyes@gmail.com (Diego 'Flameeyes' Pettenò)
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [RFC] Renaming the caps USE flag to libcap
Date: Fri, 07 Mar 2008 17:12:40 +0100 [thread overview]
Message-ID: <m2lk4u8qdj.fsf@gmail.com> (raw)
In-Reply-To: fqrjoq$eaq$1@ger.gmane.org
Tiziano Müller <dev-zero@gentoo.org> writes:
> Well, I'm not sure whether libcap is a good choice: What about
> (not-yet-existing) apps which provide capability-support through another
> package (like a foobar language libcap-wrapper)? Should they also use
> libcap then?
Uhm, good point. What about fscaps for the other case then? Or filecaps?
--
Diego "Flameeyes" Pettenò
http://blog.flameeyes.eu/
--
gentoo-dev@lists.gentoo.org mailing list
prev parent reply other threads:[~2008-03-07 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 20:56 [gentoo-dev] [RFC] Renaming the caps USE flag to libcap Diego 'Flameeyes' Pettenò
2008-03-07 14:34 ` [gentoo-dev] " Tiziano Müller
2008-03-07 16:12 ` Diego 'Flameeyes' Pettenò [this message]
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=m2lk4u8qdj.fsf@gmail.com \
--to=flameeyes@gmail.com \
--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