1 |
On 1/5/06, Neil Bothwick <neil@××××××××××.uk> wrote: |
2 |
> On Thu, 5 Jan 2006 16:08:04 +0000, Tom Martin wrote: |
3 |
> |
4 |
> > > if_blocked_by('openmotif') |
5 |
> > > ewarn "You must unmerge openmotif before proceeding" |
6 |
> > |
7 |
> > An error message like that doesn't really tell the user anything that he |
8 |
> > doesn't already know. |
9 |
> |
10 |
> It may not say anything you or I don't know, but from the number of posts |
11 |
> to this list about blockers, it would clearly help some people. |
12 |
|
13 |
Yes, and I've noticed there's a big problem with the linux community |
14 |
at large. People that know and understand linux have a lot of the |
15 |
times not helped the "open source" intiative, in that they like things |
16 |
to be difficult, because it makes them somehow seem smarter. In all |
17 |
reality, it doesn't take a genius to use linux, just someone who likes |
18 |
to read a whole lot. |
19 |
|
20 |
Now i'm not saying this is a problem with the people working on |
21 |
gentoo, so please don't think that I am. But, if you do feel that |
22 |
way, perhaps you should think twice, and actually support users. I've |
23 |
always felt that Linux in general could easily surpass windows in |
24 |
usage, *IF* the linux community would make things more user friendly. |
25 |
For example, if I didn't have to read the documentation to get |
26 |
something basic to work, then it's user friendly. That doesn't mean |
27 |
you have to remove flexibility either. I've seen gui utilities in |
28 |
windows that had full command line support. If you provide command |
29 |
line options, the GUI doesn't start. So, one can have user friendly |
30 |
applications without sacrificing flexibility. |
31 |
|
32 |
When I first started with gentoo, I was ready to give up. Not because |
33 |
I didn't know what I was doing with linux, but because I don't really |
34 |
have the time to read a whole whack of documentation, and the |
35 |
documntation is not in a nice point form format for those that do know |
36 |
what they are doing anyhow. Take the gentoo quick install version of |
37 |
the gentoo hand book. It no longer tells you what commands to |
38 |
actually run. It just describes what to do, which is of VERY little |
39 |
value. Luckily I kept a printed copy of the old quick install around, |
40 |
becuse I have no use for the new version. Why someone would remove |
41 |
all that useful information from a quick install guide, only to make a |
42 |
lot less useful, I don't know. |
43 |
|
44 |
> |
45 |
> > It would be more useful if some information was provided: |
46 |
> > |
47 |
> > if blocked_by >=x11-libs/openmotif-1.2.3 ; then |
48 |
> > eblockinfo "Due to changes with blah, it is recommended that" |
49 |
> > eblockinfo "you foobar. See http://bugs.gentoo.org/123456." |
50 |
> > fi |
51 |
> > |
52 |
> > But then, at what point would this information be echoed to the user? |
53 |
> > It would have to be during the same pre-merge phase that the blocking |
54 |
> > errors appear. |
55 |
> |
56 |
> Yes, so instead of rushing to this list or the forums, they can do what |
57 |
> the message tells them and be on their way. The current messages are only |
58 |
> useful if you already understand how and why blocks happen, and how to |
59 |
> deal with them. |
60 |
|
61 |
EXACTLY. |
62 |
|
63 |
> |
64 |
> |
65 |
> -- |
66 |
> Neil Bothwick |
67 |
> |
68 |
> If you got the words it does not mean you got the knowledge. |
69 |
> |
70 |
> |
71 |
> |
72 |
|
73 |
-- |
74 |
gentoo-user@g.o mailing list |