1 |
Thus spake Paul de Vrieze on Wed, Oct 06, 2004 at 03:32:50AM CDT |
2 |
> On Wednesday 06 October 2004 09:40, Lindsay Haisley wrote: |
3 |
> > Thus spake Gábor Farkas on Wed, Oct 06, 2004 at 02:23:59AM CDT |
4 |
> |
5 |
> > Printers are an Issue in Linux, and it's not just Gentoo. Eric Raymond |
6 |
> > sent a flame letter to the CUPS people a while back detailing his |
7 |
> > horror story of setting up a CUPS printer. His story was chillingly |
8 |
> > similar to my own experience. It was a nightmare! Maybe the Gentoo |
9 |
> > devs could pick up the ball and make CUPS a little easier to use. |
10 |
> |
11 |
> The main problem with cups is the lack of "default" supported printers. |
12 |
> One needs foomatic or gimp-print-cups to add more printers. Foomatic |
13 |
> however does not by default provide all printers it knows about to cups |
14 |
> (Just a matter of generating ppd files and putting them |
15 |
> in /usr/share/cups/model). |
16 |
|
17 |
The problem that Eric pointed out, which was what I found out too, is that |
18 |
the documentation and the UI are written by and for geeks, basically for |
19 |
geeks who are already experts on Linux printing. This is something that |
20 |
could certainly be addressed independently of the CUPS project. Once I had |
21 |
CUPS and foomatic on my system, and sweated and puzzled for a while with the |
22 |
config files, using CUPS was pretty simple and it 'just worked'. The Gentoo |
23 |
online docs for getting printing going are excellent, but didn't go the last |
24 |
mile, although it's been a while and that may have changed. Read |
25 |
<http://www.catb.org/~esr/writings/cups-horror.html> if you haven't already |
26 |
seen it. |
27 |
|
28 |
<soapbox> |
29 |
To say the least, Eric is no wilting violet when it comes to Linux software, |
30 |
but he pointed to something that's should be of concern to all of us. The |
31 |
open source equivalent of proprietary software's "tech support" that doesn't |
32 |
support is the FOSS project dev group that doesn't understand the needs of |
33 |
the non-dev community. Look at the docs on such an otherwise very useful |
34 |
project and you'll find a changelog, an API description, a FAQ with |
35 |
questions the average user would _never_ think to ask, prolly a prominent |
36 |
discussion of the license. I've run into plenty of projects which describe |
37 |
themselves in terms such as "project x is an upgrade to project y, and |
38 |
incorporates the evorgutated framus object framework from project z". Duh? |
39 |
</soapbox> |
40 |
|
41 |
<strokes> |
42 |
I've gotta add here the the Gentoo dev community has done an excellent job |
43 |
of bridging this gap in general. The best of Gentoo documentation consists |
44 |
of very explicit step-by-step HOWTOs (such as the Gentoo install stuff) |
45 |
which, if one follows them slavishly, get the job done. At the same time, |
46 |
they don't try to gloss over tech details or talk down to those of us who |
47 |
may be fairly knowledgable but don't have time to do a research project in |
48 |
order to get something configured that ought to be simple. |
49 |
</strokes> |
50 |
|
51 |
-- |
52 |
Lindsay Haisley | "Everything works | PGP public key |
53 |
FMP Computer Services | if you let it" | available at |
54 |
512-259-1190 | (Travis W. Redfish) | <http://www.fmp.com/pubkeys> |
55 |
http://www.fmp.com | ("The Roadie") | |
56 |
|
57 |
-- |
58 |
gentoo-desktop@g.o mailing list |