1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA256 |
3 |
|
4 |
On 19/01/13 05:33 AM, Rich Freeman wrote: |
5 |
> On Sat, Jan 19, 2013 at 3:18 AM, Ben de Groot <yngwin@g.o> |
6 |
> wrote: |
7 |
>> I'm not sure whether we need to keep cups at all. I haven't |
8 |
>> printed anything from my personal PC or laptop in years. And I'm |
9 |
>> sure I'm not the only one. |
10 |
> |
11 |
> The suggestion that few people actually print anything ever really |
12 |
> seems "out of touch" to me, but it could easily be |
13 |
> cultural/generational/etc, and maybe I'm the one who is out of |
14 |
> touch. |
15 |
|
16 |
I'll add to this bikeshed.. |
17 |
|
18 |
I'll agree (as i believe most will) that the days are going where |
19 |
everyone has a printer linked to their computer. However, I also hold |
20 |
the opinion that many (if not the majority) have access to a printer |
21 |
when necessary, either via their network or (in the case of laptops) |
22 |
via accessing a colleague's network. |
23 |
|
24 |
We could certainly disable/remove cups from the default profiles, and |
25 |
thus drop printing support -- but do we really want to put users into |
26 |
a situation that they will have to rebuild a bunch of stuff for those |
27 |
cases when the -do- want to print something? I think opt-out on this |
28 |
one is still a better option; if you *know* the install will never |
29 |
need to print (or act as a print server), USE="-cups" is easy enough |
30 |
to set. |
31 |
|
32 |
-----BEGIN PGP SIGNATURE----- |
33 |
Version: GnuPG v2.0.19 (GNU/Linux) |
34 |
|
35 |
iF4EAREIAAYFAlD68kMACgkQ2ugaI38ACPDaqAEAn89GvjNHOs8khpbu7wyKiuyv |
36 |
oYRBXZjhdi2Z0WNhk1cBALaT8gwMuTTJStuEHbcHZnxztgKoxczf6RNXhq4W09ZN |
37 |
=J2tZ |
38 |
-----END PGP SIGNATURE----- |