From: Arcady Genkin <agenkin-dated-1014007181.4e6186@thpoon.com>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] RFC: Overhaul of media-gfx/nvidia
Date: Mon, 04 Feb 2002 00:10:38 -0500 [thread overview]
Message-ID: <uobsf525o1.fsf@cdf.toronto.edu> (raw)
I didn't like the way 'nvidia' portage was done, and I ended up
re-doing it. In fact, I split it in two portages: nvidia-kernel and
nvidia-glx. Since I think that this can cause some controversy, I'd
like to discuss it in the mailing list. The ebuilds are available
from:
http://bugs.gentoo.org/show_bug.cgi?id=517
My version is better than the current one because:
1. It's split into two portages. (a) the current
version of the kernel driver is 1.0.2314, while the current version of
the glx library is 1.0.2313. With the current `nvidia' portage it's
unclear which one determines the version of the portage itself. (b) if one
compiles a new version of Linux kernel, he only needs to update
nvidia-kernel, and leave nvidia-glx untouched.
2. NVIDIA's own makefile overwrites some of the native files that
come with XFree. It upsets me when a package messes with the other
package's files, because if I were to update the world, the order of
update would determine the state of the system, etc. I decided to put
the contents of nvidia-glx into /opt/NVIDIA to make sure that they don't
mess with anything else.
3. nvidia-kernel now creates necessary device nodes.
4. nvidia-kernel now installs aliases.
The small downside of the new layout is that the user needs to add a
modules path to the Files section in XF86Config.
Comments?
--
Arcady Genkin
Don't read everything you believe.
next reply other threads:[~2002-02-04 5:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-04 5:10 Arcady Genkin [this message]
2002-02-04 16:04 ` [gentoo-dev] RFC: Overhaul of media-gfx/nvidia Bart Verwilst
2002-02-04 17:04 ` Arcady Genkin
2002-02-05 19:00 ` Martin Schlemmer
2002-02-05 22:01 ` Arcady Genkin
2002-02-07 3:32 ` Edward Muller
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=uobsf525o1.fsf@cdf.toronto.edu \
--to=agenkin-dated-1014007181.4e6186@thpoon.com \
--cc=gentoo-dev@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