1 |
Gilles Dartiguelongue wrote: |
2 |
> As others have said, there are already proper systems, documentation and |
3 |
> linking through other docs. Not finding this is what I'd call lazyness |
4 |
> or lack of google foo. Don't misunderstand me, some stuff can get ouf of |
5 |
> the radar of everyone, it's ok, real people are still here to point you |
6 |
> in the right direction. |
7 |
|
8 |
I think that I probably did not express my idea as well as I could have, since |
9 |
most of the responses I have gotten have echoed your thoughts that Gentoo |
10 |
does, indeed, have the facilities to achieve flexibility in logging, etc. |
11 |
|
12 |
I totally agree. Gentoo's capabilities, although not perfect, of course, are |
13 |
superlative and are a complement to its superb online doc. I think that's a |
14 |
big reason why we're all here - we see this and appreciate this. In fact, |
15 |
even when I do not include the word "gentoo" in a Google search, I more often |
16 |
than not end up at a Gentoo doc page - this is impressive. |
17 |
|
18 |
However, what I see as perhaps a missing "piece" is more conceptual: the |
19 |
important connection between the valuable info in the emerge logs (and their |
20 |
somewhat transient default nature) and what a user looks for when he/she has a |
21 |
problem with a package. Yes, users will realize this as they use Gentoo (and |
22 |
will start paying more attention to logs as a result), so I don't think it's a |
23 |
huge problem, but what this particular user said to me made me think that |
24 |
there is, perhaps, an opportunity to improve the situation. |
25 |
|
26 |
There is no Gentoo-specific "readme" facility, which could be the obvious and |
27 |
de facto place to go when trouble is had. I can imagine that a fairly simple |
28 |
and low-effort way of starting such a resource would be to simple echo the log |
29 |
output into a package-specific file in a known place (or put it in the portage |
30 |
db). The logging facilities allow similar things if configured to do it, but |
31 |
it is not on by default. Once users know where to go to see the |
32 |
"instructions" or "notes" on getting a package up and running after |
33 |
installation, this would become a good place to have such info or to expand on |
34 |
how the facility works. Starting with just the plain emerge log output would |
35 |
be an easy way to get benefit of such a concept has merit. And by no means |
36 |
would such a thing be an attempt to replace the excellent on-line docs or |
37 |
wiki, either - I see both as having unique strengths. For example, for |
38 |
detailed info on packages, the wiki/web stuff is the better resource. For a |
39 |
quick check of whether a revdep-rebuild might have been necessary after |
40 |
installing a new package would typically be in the log/notes. The notes also |
41 |
have the key advantage that they would *always* contain what the log output |
42 |
was, whereas whether a wiki or web page exists on a particular package depends |
43 |
on whether someone spent the time to author one. |
44 |
|
45 |
My intention with the RFC was to see if the concept has any worth and to kick |
46 |
it around a bit. I do not really see this as a deficiency in Gentoo's |
47 |
technology (which I have a feeling is how many here have interpreted it), but |
48 |
simply something that, if done correctly, could be useful. |
49 |
|
50 |
-Joe |