On Fri, Jan 12, 2001 at 07:32:59PM +0100, Christian Marillat wrote: > H> I don't need to work with sawfish, and I suppose may > H> make the most sense to drop the helix package sites. > > H> ==> ONE KEY QUESTION, SHOULD I BE DROPPING HELIX SITE? > > H> Could someone advise and/or point me to doc on this? > H> I run RedHat on another system and have been happy with > H> Helix, so setup my Debian to grab Helix. This worked > H> fine until about a month ago when it snapped. > > Don't mix up Helix and Debian.
This reminds me. There is a discrepancy between the dependency behavior of the Helix and Debian sawfish packages. Sawfish now looks for the GNOME libraries at runtime, and dlopens them if found. As a result, even a binary built with gnome support doesn't actively link against any GNOME libraries. For the Helix packages, I got rid of the separate configure and build step for the sawfish-gnome package. Sawfish is built and installed only once, and the sawfish-gnome package just contains the things needed for gnomecc: usr/bin/sawfish-capplet usr/share/gnome usr/share/control-center Then sawfish-gnome doesn't conflict with sawfish. You may want to consider doing this for the Debian packages. Peter
