public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Unified nVidia Driver Ebuild ready for testing
Date: Fri, 23 Dec 2005 21:49:04 +0100	[thread overview]
Message-ID: <200512232149.13748@enterprise.flameeyes.is-a-geek.org> (raw)
In-Reply-To: <pan.2005.12.23.17.41.45.627229@comcast.net>

[-- Attachment #1: Type: text/plain, Size: 672 bytes --]

On Friday 23 December 2005 18:41, Peter wrote:
> We would like your help in evaluating, testing, and
> commenting on this approach. Please locate the latest
> nvidia ebuild at:
I thought that we (gentoo devs) were trying to split the modules from ebuilds, 
so that people don't need to waste time with userland when rebuilding modules 
after kernel update.

Also, I'd really like to have nvidia-glx split from nvidia-kernel because of 
fbsd support, adding all on one ebuild would make it difficult to handle the 
fbsd case...

-- 
Diego "Flameeyes" Pettenò - http://dev.gentoo.org/~flameeyes/
Gentoo/ALT lead, Gentoo/FreeBSD, Video, AMD64, Sound, PAM, KDE

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-12-23 20:55 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         ` [gentoo-dev] " Curtis Napier
2005-12-24 20:15           ` fire-eyes
2005-12-24 20:24             ` Dale
2005-12-23 20:49 ` Diego 'Flameeyes' Pettenò [this message]
2005-12-27 15:50   ` [gentoo-dev] " 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=200512232149.13748@enterprise.flameeyes.is-a-geek.org \
    --to=flameeyes@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