BACKGROUND:
Am preparing for the xorg update, and hal wants to bring in cryptsetup:
('ebuild', '/', 'sys-fs/cryptsetup-1.0.5-r1', 'merge') pulled in by
>=sys-fs/cryptsetup-1.0.5 required by ('ebuild', '/',
'sys-apps/hal-0.5.11-r8', 'merge')
A quick look at the ebuild reveals this:
IUSE="X acpi apm crypt debug dell disk-partition doc laptop selinux
${KERNEL_IUSE}"
RDEPEND=">=dev-libs/dbus-glib-0.61
>=dev-libs/glib-2.14
>=dev-libs/expat-1.95.8
>=dev-libs/libusb-0.1.10a
>=sys-apps/pciutils-2.2.7-r1
>=dev-util/gperf-3.0.3
sys-apps/usbutils
virtual/eject
amd64? ( >=sys-apps/dmidecode-2.7 )
dell? ( >=sys-libs/libsmbios-0.13.4 )
disk-partition? ( >=sys-apps/parted-1.8.0 )
ia64? ( >=sys-apps/dmidecode-2.7 )
kernel_linux? (
>=sys-fs/udev-117
>=sys-apps/util-linux-2.13
>=sys-kernel/linux-headers-2.6.19
crypt? ( >=sys-fs/cryptsetup-1.0.5 )
)
(I'm aware of the udev vs cryptsetup workaround listed in bugzilla)
QUESTIONS:
1. Is cryptsetup really necessary on non-encrypted systems? It appears
to be both setting, and then testing for crypt. If it does require
cryptsetup, then Why?
2. I'm using loop-aes. If the answer to question number 1 is yes, then
will hal have an issue with loop-aes/loop devices?
Thanks in advance....... Newbie
