On 4/13/07, Alexander E. Patrakov <[EMAIL PROTECTED]> wrote: > > since r6723, Python is an optional, not required dependency of HAL. However, > there might be applications in BLFS that depend on Python and HAL. Before > the commit, the Python dependency was implicit, because HAL unconditionally > depended on Python. This is no longer the case, so information about > dependencies of some packages in the book is probably inaccurate. If you > find any such inaccuracy, please fix it.
I'm pretty familiar with HAL/Python. I was just looking at it the other day. Actually, I was looking at HAL-0.5.9, but I remember the same for 0.5.7.1. I think it was just an oversight by the developers. It's only used in the hal-device-manager pygtk app. The only reason it's "required" is because they used the autoconf macro AM_PATH_PYTHON which by default errors if it didn't find python. If you grep through for PYTHON, though, you'll see it's only used in the tools/device-manager directory. I'll ask on the hal list for sure. I know he's planning on making a 0.5.9.1 bugfix release real soon, so maybe we can get that in the tarball before then. > Below is the list of packages that should be rechecked for Python > dependencies: > > multimedia/cdwriteutils/k3b.xml > multimedia/libdriv/gst-plugins-good.xml > kde/core/kdelibs.xml > kde/core/kdebase.xml > xsoft/office/evolution.xml > gnome/add/gnome-volume-manager.xml > gnome/add/gnome-utils.xml > gnome/add/nautilus-cd-burner.xml > gnome/add/gnome-mount.xml > gnome/add/epiphany.xml > gnome/core/gnome-applets.xml > gnome/core/gnome-vfs.xml All of those use either the dbus-glib bindings or the dbus-qt3 bindings to work with HAL. They shouldn't be affected by python in any way. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
