From: Curtis Napier <curtis119@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Unified nVidia Driver Ebuild ready for testing
Date: Sat, 24 Dec 2005 15:00:47 -0500 [thread overview]
Message-ID: <43ADA8EF.1010406@gentoo.org> (raw)
In-Reply-To: <43AD1205.1050403@exceedtech.net>
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
next prev parent reply other threads:[~2005-12-24 20:04 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-23 17:41 [gentoo-dev] Unified nVidia Driver Ebuild ready for testing Peter
2005-12-23 18:47 ` Mike Frysinger
2005-12-23 19:05 ` [gentoo-dev] " Peter
2005-12-23 20:13 ` Stuart Herbert
2005-12-23 20:40 ` [gentoo-dev] " Peter
2005-12-23 19:43 ` [gentoo-dev] " Stephen P. Becker
2005-12-23 19:59 ` [gentoo-dev] " Peter
2005-12-23 20:15 ` Stephen P. Becker
2005-12-24 8:47 ` Niklas Bolander
2005-12-24 9:16 ` Dale
2005-12-24 11:34 ` [gentoo-dev] " Peter
2005-12-24 11:44 ` Dale
2005-12-24 12:09 ` Carsten Lohrke
2005-12-24 12:50 ` [gentoo-dev] " Peter
2005-12-24 13:09 ` Diego 'Flameeyes' Pettenò
2005-12-24 15:31 ` [gentoo-dev] " Peter
2005-12-24 15:58 ` Diego 'Flameeyes' Pettenò
2005-12-24 21:27 ` [gentoo-dev] " R Hill
2005-12-24 13:52 ` [gentoo-dev] Re: " Jon Portnoy
2005-12-24 14:29 ` Carsten Lohrke
2005-12-24 14:57 ` Jean-Francois Gagnon Laporte
2005-12-24 20:30 ` lnxg33k
2005-12-24 17:35 ` Ciaran McCreesh
2005-12-24 19:49 ` Jan Kundrát
2005-12-26 11:25 ` Rodolfo Boer
2005-12-24 20:00 ` Curtis Napier [this message]
2005-12-24 20:15 ` [gentoo-dev] " fire-eyes
2005-12-24 20:24 ` Dale
2005-12-23 20:49 ` [gentoo-dev] " Diego 'Flameeyes' Pettenò
2005-12-27 15:50 ` Henrik Brix Andersen
2005-12-27 17:55 ` [gentoo-dev] " Peter
2005-12-27 18:42 ` Diego 'Flameeyes' Pettenò
2005-12-24 10:00 ` R Hill
2005-12-28 0:06 ` [gentoo-dev] " Paweł Madej
2005-12-28 18:40 ` [gentoo-dev] " Peter
2005-12-28 23:54 ` fire-eyes
2005-12-30 17:54 ` Chris Gianelloni
2006-01-01 1:12 ` Ciaran McCreesh
2006-01-02 13:31 ` Tres Melton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43ADA8EF.1010406@gentoo.org \
--to=curtis119@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox