1 |
On Mon, 2005-11-07 at 21:32 +0900, Jason Stubbs wrote: |
2 |
> On Monday 07 November 2005 19:22, Paul Waring wrote: |
3 |
> > When one of the key complaints about Linux is that the documentation is |
4 |
> > often lacking, I'm surprised to see a distro with some of the best |
5 |
> > manuals considering doing away (or at least hiding somewhere else) with |
6 |
> > parts of it. |
7 |
> |
8 |
> It's not about the documentation. It's mostly about portage actually. Certain |
9 |
> sets of USE flags create circular dependencies that portage doesn't deal with |
10 |
> well or at all. Packages then fail to build and bugs get posted. What did the |
11 |
> user do wrong? Nothing. What can the user do? Figure out where the circular |
12 |
> dependency is and manually solve it. Should the steps on how to do that be |
13 |
> added to the Stage1/2 install guide? I'd think not. |
14 |
|
15 |
Correct. Not only are circular dependencies an issue, but dependencies |
16 |
that break the flow of the Handbook are quite common. A prime example |
17 |
is hal. There are combinations of USE flags that will pull in hal as a |
18 |
dependency when doing "emerge -e system" to go from stage2 to stage3. |
19 |
The problem is that the Handbook does not have the user install a kernel |
20 |
*prior* to stage3. The user does not have a configured kernel, nor even |
21 |
sources installed. The sources for the default kernel virtual are |
22 |
installed, whether the user wants these sources or not, and hal looks |
23 |
for a kernel configuration, then fails when it cannot find one. How |
24 |
exactly would you document this? |
25 |
|
26 |
-- |
27 |
Chris Gianelloni |
28 |
Release Engineering - Strategic Lead |
29 |
x86 Architecture Team |
30 |
Games - Developer |
31 |
Gentoo Linux |