


197 builds fine with latest sys-libs/uclibc in Portage. I'm also happy with the build system and the current 197 ebuild. There are people who still want to use latest original udev with OpenRC.prometheanfire wrote:sys-fs/eudev-1_beta2-r1 is based on 197, we've made it more compatible with other libs (not just glibc) and redid the build system to something sane (previously, building udev required building systemd for some reason...).



http://forums.gentoo.org/viewtopic-p-75 ... ml#7565312duderonomy wrote:Can somebody post a link or simple direction for using EUdev?
thx!
haarp wrote:Does eudev use hwdb?
equery u eudev
[ Legend : U - final flag setting for installation]
[ : I - package is installed with flag ]
[ Colors : set, unset ]
* Found these USE flags for sys-fs/eudev-1.5.3-r1:
U I
- - doc : Add extra documentation (API, Javadoc, etc). It is recommended to enable
per package instead of globally
- - gudev : enable libudev gobject interface
+ + hwdb : read vendor/device string database and add it to udev database
- - introspection : Use dev-libs/gobject-introspection for introspection
+ + keymap : map custom hardware's multimedia keys
- - kmod : enable module loading through libkmod
+ + modutils : enable module loading support - use modutils calls if kmod not enabled
+ + openrc : install the OpenRC init scripts
+ + rule-generator : install legacy rule generator rules and support scripts - note that the
functionality within was dropped from sys-fs/udev as it is not stable in
all cases; use at your own risk
- - static-libs : Build static versions of dynamic libraries as well
- - test : Workaround to pull in packages needed to run with FEATURES=test.
Portage-2.1.2 handles this internally, so don't set it in
make.conf/package.use anymore