| 1 |
On 11/12/2013 23:04, Mick wrote: |
| 2 |
> On Wednesday 11 Dec 2013 16:52:49 Peter Humphrey wrote: |
| 3 |
>> On Wednesday 11 Dec 2013 18:39:59 Alan McKinnon wrote: |
| 4 |
>>> $ equery depends print-manager |
| 5 |
>>> |
| 6 |
>>> * These packages depend on print-manager: |
| 7 |
>>> kde-base/kdeutils-meta-4.11.4 (cups ? |
| 8 |
>>> |
| 9 |
>>>> =kde-base/print-manager-4.11.4:4[aqua=]) |
| 10 |
>>> |
| 11 |
>>> Set USE="-cups" to fix |
| 12 |
>> |
| 13 |
>> Confirmed. I didn't have kdeutils-meta installed. Installing it pulls in 10 |
| 14 |
>> packages with USE=-cups, 21 without. I'm installing it now. |
| 15 |
>> |
| 16 |
>> Of course I want other programs to be able to print, so I only set -cups |
| 17 |
>> against kdeutils-meta. |
| 18 |
> |
| 19 |
> Let me get this right, if I set 'kde-base/kdeutils-meta -cups' I will still be |
| 20 |
> able to print from kde applications? |
| 21 |
> |
| 22 |
|
| 23 |
|
| 24 |
I believe so. As far as I could ever tell, KDE's print manager was just |
| 25 |
a configurator front end to CUPS, so you can configure CUPS directly |
| 26 |
instead. |
| 27 |
|
| 28 |
For many years, that's exactly what I did. The print manager was masked |
| 29 |
for years as "broken by design" and at one point wasn't even installed |
| 30 |
by default at all. So I got used to hitting port 631 on localhost in a |
| 31 |
browser. |
| 32 |
|
| 33 |
I can't see any reason why it still isn't like that |
| 34 |
|
| 35 |
-- |
| 36 |
Alan McKinnon |
| 37 |
alan.mckinnon@×××××.com |
Archives