public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Matthias Schwarzott <zzam@gentoo.org>
Subject: Re: [gentoo-dev] About udev-145: new features / extras and kernel requirements
Date: Mon, 09 Nov 2009 18:35:54 +0200	[thread overview]
Message-ID: <1257784554.16908.3.camel@localhost> (raw)
In-Reply-To: <200908301611.53087.zzam@gentoo.org>

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

On Sun, 2009-08-30 at 16:11 +0200, Matthias Schwarzott wrote:
> Hi there!

A late hello,

> Second point: udev-145 bundles a lot of new extras, but they can only be 
> enabled/disabled all or nothing.
> 
> These extras are:
> * udev-acl: Apply consolekit permissions to devices for users (audio, video, 
> joysticks, scanner, cameras, ...)
> * usb-db: Provide udev-rules with device names of pci and usb devices
> * hid2hci: Special utility to fix resume of some hid devices
> * keymap: Auto-configure model specific keys found on many laptops 
> ("brightness up", "next song", "www browser", or "suspend")
> * modem-modeswitch: Switch modems that provide virtual cd-drive with drivers 
> to modem mode

I think the thread hasn't seen an answer to the question of when these
are actually used or useful, as asked in another subthread as well.

> * gudev: glib/gobject support for libudev

Would it be possible to have this in a separate package? Of course then
with a temporary compatibility PDEPEND on it with udev[extras] until
packages needing gudev migrate over.
And what of the above listed other things besides core udev does gudev
require or potentially use?

> This makes udev depend on these libs:
> libacl, libglib2, libusb, usbutils, pciutils, gperf
> 
> Up to now I have just added use-flag "extras" to control these. But I suppose 
> that udev-acl and maybe gudev is a hard requirement for newer hal or 
> devicekit versions. And upstream thinks these should be enabled by default.
> 
> Are any of these extras considered harmful?

On some non-desktop systems perhaps, yes.

-- 
Mart Raudsepp
Gentoo Developer
Mail: leio@gentoo.org
Weblog: http://planet.gentoo.org/developers/leio

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2009-11-09 16:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-30 14:11 [gentoo-dev] About udev-145: new features / extras and kernel requirements Matthias Schwarzott
2009-08-30 14:24 ` Arun Raghavan
2009-08-30 15:26   ` [gentoo-dev] " Duncan
2009-08-30 14:46 ` [gentoo-dev] " Nirbheek Chauhan
2009-08-30 15:45   ` William Hubbs
2009-08-30 16:18     ` Mike Auty
2009-08-31 15:46     ` Jeremy Olexa
2009-08-31  4:25   ` Lars Wendler
2009-08-30 15:05 ` Bruno
2009-08-30 19:20   ` Robin H. Johnson
2009-11-09 16:35 ` Mart Raudsepp [this message]
2009-11-12  9:08   ` Matthias Schwarzott
2009-11-09 19:22 ` Daniel Drake

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