Re: [HPLIP-Devel] Packaging qt-dependent HPLIP parts separately

2007-04-05 Thread Sven Utcke
Hi, For the record, below is the current split that I needed for HPLIP-1.7.2. It would be very much appreciated if this split could be made easier by the HPLIP developers..! Needed for core operation on a Qt-less machine: let me just add that I would also very much appreciate a better

Re: [HPLIP-Devel] Packaging qt-dependent HPLIP parts separately

2007-04-04 Thread Tim Waugh
On Tue, 2006-06-27 at 09:23 -0700, dwelch91 wrote: One correction, hp-print would also be in this list. -Don dwelch91 wrote: Tim, I think for the purposes of a Qt-less HPLIP, you could create a RPM without: toolbox.py sendfax.py* fab.py* ui/ directory* plugins/ directory

Re: [HPLIP-Devel] Packaging qt-dependent HPLIP parts separately

2006-06-27 Thread Johannes Meixner
Hello, On Jun 26 17:52 Tim Waugh wrote (shortened): When packaging HPLIP as RPMs I'd like to be able to separate out the parts that require qt from those that don't. Is there an easy way to distinguish the two sets of files I need? I assume what you really want is some kind of base package

Re: [HPLIP-Devel] Packaging qt-dependent HPLIP parts separately

2006-06-27 Thread Tim Waugh
On Tue, 2006-06-27 at 11:56 +0200, Johannes Meixner wrote: I assume what you really want is some kind of base package which can actually be used and installed without any graphical stuff (e.g. so that HPLIP can be used on a server without pulling in tons of graphical stuff)? Yes, this is

Re: [HPLIP-Devel] Packaging qt-dependent HPLIP parts separately

2006-06-27 Thread Henrique de Moraes Holschuh
On Tue, 27 Jun 2006, dwelch91 wrote: 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. Is this configure flag useful then? Not to Debian, and probably not for other