Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 113361 - OpenOffice 2.0.0 does not compil with other print system than cups
Summary: OpenOffice 2.0.0 does not compil with other print system than cups
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High enhancement (vote)
Assignee: Gentoo Office Team
URL:
Whiteboard:
Keywords:
: 114074 117293 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-11-23 08:40 UTC by Yannis Avenel
Modified: 2006-01-01 05:16 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yannis Avenel 2005-11-23 08:40:50 UTC
app-office/openoffice 2 needs CUPS to compil. It should be great if it could use
other print system such as lprng.



Reproducible: Always
Steps to Reproduce:
1. Have a gentoo without cups
2. emerge -DNauv openoffice
3. emerge wants to install cups

Actual Results:  
[blocks B     ] net-print/lprng (is blocking net-print/cups-1.1.23-r1)
[ebuild  N    ] net-print/cups-1.1.23-r1

Expected Results:  
emerge should have compil OpenOffice 2 with the default print system (lprng in
this case)
Comment 1 Paul de Vrieze (RETIRED) gentoo-dev 2005-11-24 01:50:43 UTC
It would be nice. Print systems such as lprng do however not support printer
features as much as cups can, so I understand why upstream uses CUPS. Cups
support is however optional at runtime, so you might after the building of
openoffice, re-install lprng and use openoffice with slightly degraded
functionality. The bottom line though is that currently building without cups is
not easy, and something for upstream to fix.
Comment 2 Jakub Moc (RETIRED) gentoo-dev 2005-11-30 15:42:39 UTC
*** Bug 114074 has been marked as a duplicate of this bug. ***
Comment 3 Jakub Moc (RETIRED) gentoo-dev 2006-01-01 05:16:46 UTC
*** Bug 117293 has been marked as a duplicate of this bug. ***