On Tue, 27 Jun 2006, Suffield, David wrote: > Based on your feedback for a qt-less configuration. I think the > following configuration option can be added to a future HPLIP release. > > --disable-qt-build (default = no) > > This option would be used to build a no-gui (command line only) HPLIP > configuration. With "qt-build=yes", no "qt-required" applications would > be installed and "qt-optional" applications would default to no-gui.
I think we were talking about slightly different things. My understanding, as a downstream maintainer, is that the distros would still want to build the GUI and non-GUI parts in one go, and package them apart in different binary packages (instead of providing two overlapping sets of binary packages, one with and one without GUIs). However, if it would make your life easier to run the build twice with different configure options when one wants a non-gui mode, it should not be a problem for us either. When I talked about a system-wide config for GUIness or non-GUIness, I was thinking more of something in the main /etc/hp/hplip.conf, a "master switch of sorts", where one could disable the GUIs in two-mode programs. This thought came from your comment about a "config file". As for using the existence of "DISPLAY" to detect wether to run in GUI-mode or not, is a good way to do it (it is not a hack, it is a proper way to take that decision). I'd suggest doing it like this: In priority order, I'd suggest the following for selecting non-gui mode: 1. Set auto or non-gui, depending on command line switches 2. Set auto or non-gui, depending on master setting in hplip.conf Of course, "auto" means "enable GUI if DISPLAY is set, run in non-gui mode otherwise". If HPLIP was built with --disable-qt-build, code that outputs an error message if a GUI is requested should be put in place. And when in non-GUI mode, please make sure the code doesn't import/link to python-qt modules, at all. These modules often do stupid things at initialization time even when no GUI is running, so it is better to *really* not even attempt to load them if you are not going to use a GUI. Someday I will take a bored-as-heck moment to track down why the pyqt compiler thinks it has a business trying to contact KDE in a build-daemon, delaying the build and sending out error messages, for example :-) -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ HPLIP-Devel mailing list HPLIP-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hplip-devel
