On Sat, 25 Feb 2012 at 19:38:21 +0100, Kamil Rytarowski wrote: > On 25.02.2012 13:13, Carlos R. Mafra wrote: > >On Sat, 25 Feb 2012 at 12:45:46 +0100, Rodolfo García Peñas wrote: > >>On Sat, 25 Feb 2012, Kamil Rytarowski escribió: > >> > >>>Thank you for this suggestion. So for now I have: > >>>- old GNUstep button (to configure Window Maker) > >>>- terminal > >>>- distro specific configurator (Mageia Control Center) > >>>- wmcalclock > >>>- wmsystemtray > >>>- wmudmount > >>> > >>>In the autostart: > >>>- nm-applet > >>I don't like nm-applet: > >> > >>Depends: libatk1.0-0 (>= 1.12.4), libc6 (>= 2.4), libcairo-gobject2 (>= > >>1.10.0), libcairo2 (>= 1.2.4), libdbus-1-3 (>= 1.0.2), libdbus-glib-1-2 (>= > >>0.88), libfontconfig1 (>= 2.8.0), libfreetype6 (>= 2.2.1), libgconf2-4 (>= > >>2.31.1), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.24.0), > >>libgnome-bluetooth8 (>= 2.91.2), libgnome-keyring0 (>= 3.2.2-2~), > >>libgtk-3-0 (>= 3.0.0), libnm-glib-vpn1 (>= 0.7.999), libnm-glib4 (>= > >>0.8.998), libnm-gtk0 (>= 0.9.1.95), libnm-util2 (>= 0.8.998), libnotify4 > >>(>= 0.7.0), libpango1.0-0 (>= 1.14.0), gconf2 (>= 2.28.1-2), > >>network-manager (>= 0.9.2), policykit-1-gnome, gnome-icon-theme, dbus-x11 > >Do you have a better alternative? That's not a rethorical question, > >I really want to know what other people do. > > > >But for the same reasons I prefer the simple wmvolman over wmudmount > >because wmudmount pulls a lot of libraries (but probably the same ones > >as nm-applet). > The lists: [1] > Requirements of wmudmount > libX11.so.6 > libc.so.6 > libc.so.6(GLIBC_2.0) > libc.so.6(GLIBC_2.1) > libc.so.6(GLIBC_2.3) > libc.so.6(GLIBC_2.3.4) > libc.so.6(GLIBC_2.4) > libc.so.6(GLIBC_2.9) > libdbus-1.so.3 > libdbus-glib-1.so.2 > libgdk-x11-2.0.so.0 > libgio-2.0.so.0 > libglib-2.0.so.0 > libgnome-keyring.so.0 > libgobject-2.0.so.0 > libgtk-x11-2.0.so.0 > libm.so.6 > libm.so.6(GLIBC_2.1) > libnotify.so.4 > libpthread.so.0 > libpthread.so.0(GLIBC_2.0) > libpthread.so.0(GLIBC_2.1) > rtld(GNU_HASH) > > Requirements of networkmanager-plugin: > libc.so.6 > libc.so.6(GLIBC_2.0) > libc.so.6(GLIBC_2.1) > libc.so.6(GLIBC_2.1.3) > libc.so.6(GLIBC_2.2) > libc.so.6(GLIBC_2.3) > libc.so.6(GLIBC_2.3.4) > libc.so.6(GLIBC_2.4) > libcairo.so.2 > libdbus-1.so.3 > libdbus-glib-1.so.2 > libgconf-2.so.4 > libgdk-3.so.0 > libgdk_pixbuf-2.0.so.0 > libglib-2.0.so.0 > libgmodule-2.0.so.0 > libgnome-bluetooth.so.10 > libgnome-keyring.so.0 > libgobject-2.0.so.0 > libgtk-3.so.0 > libnm-glib-vpn.so.1 > libnm-glib.so.4 > libnm-gtk.so.0 > libnm-util.so.2 > libnotify.so.4 > libpango-1.0.so.0 > libpangocairo-1.0.so.0 > libpthread.so.0 > libpthread.so.0(GLIBC_2.0) > networkmanager > rtld(GNU_HASH) > > So it's comparable, and the dependencies are similar. > > From the Arch Linux wiki: > "HAL has become deprecated in favor of udev, udisks, upower, etc. > and is no longer developed. Currently, a small number of programs > still rely on and use HAL, though development is heading toward > utilizing udev as a replacement." [2] So I prefer to maintain Udisk > one.. without caring of a few additional dependencies.
Why do you mention HAL? wmvolman does not depend on HAL anymore, it uses udisks. -- To unsubscribe, send mail to [email protected].
