On Sat, 24 Dec 2005 03:16:53 -0600, Dale wrote: > Niklas Bolander wrote: snip...
> I have to agree. Do it sort of like KDE, with kde, kde-meta or as > seperate packages. Have it so you can pull in all three in one emerge > command but have the option to do it seperately as well. I have only > emerged glx once and do the nvidia-kernel when I change kernels. I > really don't have any use for the settings package, as long as my GUI > works anyway. > > Just give us some options. We'll be happy then. > > THAT is a very reasonable comment! Thank you Dale and everyone else who commented. Please do not think this was an attempt to shove anything down anyone's throat. It was not. That's why this thread was started and that is why we wanted feedback. Those who commented that settings and xconfig are optional _are_ correct. They are in no way required and indeed many people would not use them even if they could. Since they were so small, I wanted to see if unifying the ebuilds would make sense. Reasonable people can debate whether or not having glx installed each time a kernel is updated is worth it. It is _NOT_ required, but glx compiles nothing. They are libraries copied into a directory tree. So, there _is_ overhead when glx is installed -- such as unpacking the tarball and going through all the emerge preamble stuff. Having it wedded to kernel driver can save time even if glx is not required at the time. AND LET ME APOLOGIZE for the ebuild borking. A symlink directory was changed inadvertently between 8174 and 8178. Something changed in portage 2.0.53 which blew up the download section. I posted workarounds at the bug report. http://bugs.gentoo.org/show_bug.cgi?id=116085#c37 http://bugs.gentoo.org/show_bug.cgi?id=116085#c42 Please continue to provide additional feedback to the bug report. Happy Hanukkah, Merry Christmas. Trivia fact: first time since 1959 they start on the same day. -- gentoo-dev@gentoo.org mailing list
