From: Alexandre Rostovtsev <tetromino@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [rfc] Which ebuild category should these ebulds go into?
Date: Wed, 01 Feb 2012 03:16:21 -0500 [thread overview]
Message-ID: <1328084181.8348.6.camel@rook> (raw)
In-Reply-To: <4F28D54B.9020407@gentoo.org>
On Wed, 2012-02-01 at 07:01 +0100, Sebastian Pipping wrote:
> spacenavd
> driver daemon (with optional X support)
> --> sys-apps/spacenavd ?
> --> app-misc/spacenavd ?
> --> .. ?
I would suggest either sys-apps or x11-drivers.
> libspnav
> library accessing before-mentioned daemon
> --> dev-libs/libspnav ?
> --> media-libs/libspnav ?
> --> sys-libs/libspnav ?
> --> .. ?
dev-libs seems reasonable.
sys-libs definitely feels wrong, libspnav would look out of place in
that exclusive company of core system libraries.
-Alexandre
next prev parent reply other threads:[~2012-02-01 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 6:01 [gentoo-dev] [rfc] Which ebuild category should these ebulds go into? Sebastian Pipping
2012-02-01 8:16 ` Alexandre Rostovtsev [this message]
2012-02-01 8:42 ` ScytheMan
2012-02-01 18:26 ` Sebastian Pipping
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=1328084181.8348.6.camel@rook \
--to=tetromino@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