Bug 65587

Summary: qt requires on libcups.so ???
Product: [Retired] Red Hat Linux Reporter: pogosyan
Component: qtAssignee: Than Ngo <than>
Status: CLOSED NEXTRELEASE QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: low    
Version: 7.3   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-08-04 20:38:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description pogosyan 2002-05-28 04:32:38 UTC 
Description of Problem:
qt rpm packages dependences are astonishing - all depend on libcups.so.2 !!
What,  particular printing system is required to use qt toolkit ?


Version-Release number of selected component (if applicable):
qt-3.0.3-11 and related qt packages

How Reproducible:


Steps to Reproduce:
1. 
2. 
3. 

Actual Results:


Expected Results:


Additional Information:
Comment 1 Bernhard Rosenkraenzer 2002-06-10 14:18:01 UTC 
This is intentional.  
  
Qt is a very powerful toolkit - it includes support for printing (code-wise,  
this is very comfortable - you just treat the printer like the screen).  
  
It needs to get a list of available printers. With lpd/LPRng, the only way to  
do this is to parse /etc/printcap (and every application uses its own way to  
do that -- rather messy). With CUPS, you get libcups, and an application just  
calls a function and has a list of printers.  
  
Because of this, Qt requires the CUPS *libraries* to support printing with 
CUPS. It does NOT require the actual CUPS spooler to be used.
Comment 2 Bill Nottingham 2006-08-04 20:38:07 UTC 
Red Hat Linux and Red Hat Powertools are currently no longer supported by Red
Hat, Inc. In an effort to clean up bugzilla, we are closing all bugs in MODIFIED
state for these products.

However, we do want to make sure that nothing important slips through the
cracks. If, in fact, these issues are not resolved in a current Fedora Core
Release (such as Fedora Core 5), please open a new issues stating so. Thanks.