| 1 |
On Friday 23 December 2005 20:59, Peter wrote: |
| 2 |
> > I can tell you that I would be disappointed if this replaces the current |
| 3 |
> > ebuilds, because I really don't need to reinstall nvidia-settings and |
| 4 |
> > nvidia-glx every time I build a new kernel. |
| 5 |
> |
| 6 |
> That's why we are having this dialog. When I proposed doing a unified |
| 7 |
> ebuild, the objective always was to get and encourage feedback. If you are |
| 8 |
> happy keeping up with three ebuilds, then that is feedback we need to |
| 9 |
> have. BTW, please post these comments to the bug report. |
| 10 |
> |
| 11 |
> >> We hope you will find this approach a more streamlined and easy |
| 12 |
> >> implementation for nVidia. |
| 13 |
> > |
| 14 |
> > I don't particularly see how it is easier. |
| 15 |
> |
| 16 |
> But many do. This mirrors the approach nvidia takes. |
| 17 |
> |
| 18 |
|
| 19 |
As another non-dev/user I must say that three separate ebuilds is preferable. |
| 20 |
The kernel ebuild must be recompiled every time I change kernel while the glx |
| 21 |
only needs to be installed once. Finaly, I have rather bad experiences of |
| 22 |
nvidia-settings and would like to avoid them at all. |
| 23 |
|
| 24 |
Wouldn't it be more sensible to make a nvidia-meta build that pulled in all |
| 25 |
three if the goal is pure simplicity? |
| 26 |
|
| 27 |
Merry Christmas btw. |
| 28 |
|
| 29 |
/Niklas |
Archives