1 |
>>>>> On Tue, 21 Feb 2017, Lars Wendler wrote: |
2 |
|
3 |
>> 1) Putting printer drivers into "net-print" is silly. |
4 |
>> |
5 |
>> Something that converts format a to device-specific format b has |
6 |
>> absolutely nothing to do with network. |
7 |
>> So, a new category "sys-print", emphasizing that it's hardware |
8 |
>> drivers, (or "cups-drv"?) (or maybe "media-print"?) might make sense. |
9 |
|
10 |
> Like I said in IRC, I'm all in favor of this. "media-print" seems |
11 |
> reasonable as I don't consider printing related packages being |
12 |
> system-relevant (and thus no sys-print). |
13 |
|
14 |
+1 |
15 |
|
16 |
If the category is badly named, move the packages to something more |
17 |
reasonable. Users don't expect printer drivers in net-*. (Also I |
18 |
don't buy the argument that package moves won't be worth the effort. |
19 |
Not doing the move means that any future packages will also have an |
20 |
inappropriate name.) |
21 |
|
22 |
No large preference for either media-print or sys-print here. |
23 |
|
24 |
>> 2) After introducing that, however, "net-print" becomes nearly empty. |
25 |
>> |
26 |
>> On a quick glance, the only *network*-specific packages in there are |
27 |
>> cups and lprng. Maybe one or two more which I dont recognize. |
28 |
|
29 |
Do a complete move please. Leaving a category with two packages |
30 |
doesn't make any sense. |
31 |
|
32 |
Ulrich |