1 |
Apparently, though unproven, at 22:51 on Monday 15 November 2010, Grant |
2 |
Edwards did opine thusly: |
3 |
|
4 |
> On 2010-11-15, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
5 |
> > Apparently, though unproven, at 17:31 on Monday 15 November 2010, Grant |
6 |
> > |
7 |
> > Edwards did opine thusly: |
8 |
> >> On 2010-11-14, Mick <michaelkintzios@×××××.com> wrote: |
9 |
> >> > Finally, if xorg-server-1.8 is around the corner to be stabilised I |
10 |
> >> > suggest that you unmask it and use the xorg.conf file that we all |
11 |
> >> > know and love. :-) |
12 |
> >> |
13 |
> >> Using xorg.conf with 1.7 is simple enough (it's what I do on all my |
14 |
> >> other machines). That's why I don't understand why the Gentoo |
15 |
> >> developers decided to use HAL by default when it seems to be widely |
16 |
> >> acknowledged to be such a disaster. |
17 |
> > |
18 |
> > The Gentoo devs made no such decision. |
19 |
> > |
20 |
> > Upstream did. |
21 |
> > |
22 |
> > Gentoo closely tracks upstream, unless upstream is completely broken. |
23 |
> > HAL might be a crock of chit, but it does not render X broken and not |
24 |
> > usable. |
25 |
> |
26 |
> Whether Xorg uses HAL or not is controlled by a USE flag isn't it? So |
27 |
> upstream choses the defaults for USE flags? |
28 |
|
29 |
No, upstream chooses the default config out of the box. |
30 |
|
31 |
Gentoo does what Gentoo has to do to replicate that config. |
32 |
Gentoo needs a very good reason to change upstream default behaviour, along |
33 |
the lines of extreme brokenness. |
34 |
|
35 |
-- |
36 |
alan dot mckinnon at gmail dot com |