Dale wrote:
Niklas Bolander wrote:
On Friday 23 December 2005 20:59, Peter wrote:
I can tell you that I would be disappointed if this replaces the
current
ebuilds, because I really don't need to reinstall nvidia-settings and
nvidia-glx every time I build a new kernel.
That's why we are having this dialog. When I proposed doing a unified
ebuild, the objective always was to get and encourage feedback. If
you are
happy keeping up with three ebuilds, then that is feedback we need to
have. BTW, please post these comments to the bug report.
We hope you will find this approach a more streamlined and easy
implementation for nVidia.
I don't particularly see how it is easier.
But many do. This mirrors the approach nvidia takes.
As another non-dev/user I must say that three separate ebuilds is
preferable. The kernel ebuild must be recompiled every time I change
kernel while the glx only needs to be installed once. Finaly, I have
rather bad experiences of nvidia-settings and would like to avoid them
at all.
Wouldn't it be more sensible to make a nvidia-meta build that pulled
in all three if the goal is pure simplicity?
Merry Christmas btw.
/Niklas
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.
Ditto. A unified build would make more work for my tired old CPU. A meta
build would be better, give us the choice to pull it all in or one at a
time like kde.
ps. I appreciate the original intention of trying to clean this up. Thanks!
--
gentoo-dev@gentoo.org mailing list
