E-mail sent to www@gentoo.org: http://www.gentoo.org/doc/en/dri-howto.xml needs to be updated to reflect that the package x11-drm will not compile with 2.4 kernels. Its a bit of a pain to compile a brand new 2.6.10 kernel *without* DRM just to find out that I have to recompile the kernel with it included when emerge x11-drm says 'oh, this package doesnt support 2.6 kernels yet. please enable drm in your kernel.'
looked for duplicate, didn't find one. should be a quick fix, just something to mention that the package is 2.4 specific (the ebuild mentions it, but by the time you get that far in the instructions, you've already compiled your kernel). also Im considering a bug to suggest that every documentation page has a link to bugzilla. My first instict was to click the only thing available to me to report the error in the documentation, which was the 'email the webmaster' link. web pages controlled by the docs team should have a link on them that brings you to the bugzilla search page with the URL autofilled, so you can see if anyone has already posted the error youre submitting.
Now I'm noting this: "If you find bugs in our documentation or have proposals, please use our Bugtracking System and fill in a bug report for "Docs-developer" or "Docs-user". These bug reports will then be handled by the Gentoo Documentation Project." on http://www.gentoo.org/doc/en/index.xml Also as many times as Ive looked at g.o documentation, it didn't occur to me to just emailing the document author for corrections. I saw '...Corrections? mailto:www@gentoo.org' at the bottom of the page and didn't think about different maintainers for different documents. Do we want the proper procedure for reporting errors in documentation to be emailing the author directly, or submitting a bug to bugzilla with the docs-user team responsible? Im sure other people might be a little more responsible and put more effort into reporting documentation errors than I have. I don't think anything needs to be done since some documentation has a 'Feedback' section, and all documentation includes a link to email the author on the right hand side. (Also, since I finally saw the comment saying to contact Donnie Berkholz for feedback and that he's the author of the URL (really didn't do my homework on this), I'm adding him to the cc list.)
Well, the latest versions do work with 2.6. They apparently haven't made it to stable yet. CC'd the maintainer.
I've updated the guide to reflect the 2.6-kernel situation. It's an easy fix, I hope we'll get pinged when one of the -2005* becomes stable.
