public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter <pete4abw@comcast.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: Unified nVidia Driver Ebuild ready for testing
Date: Wed, 28 Dec 2005 13:40:34 -0500	[thread overview]
Message-ID: <pan.2005.12.28.18.40.33.680027@comcast.net> (raw)
In-Reply-To: 43B1D713.5000403@quanteam.info

On Wed, 28 Dec 2005 01:06:43 +0100, Pawe Madej wrote:

> In my opinion if you want to build monolitic ebuild in system like
> gentoo where everything is going to be modular you should try some local
> USE flags for example monolitic to install all the stuff you are puting
> into it and of cours flags for every part which could be istalled
> independly.
> 
> As a common user i need only nvidia-kernel and its dependency nvidia-glx
> to be happy.
> 
> Greets
> Pawel Madej

Thanks for your feedback from the user POV. You point out part of the
current problem. glx is NOT a dependency of kernel. So a user who installs
kernel will NOT get glx under the current situation. This will cause
nvidia to fail at startup.

This is because glx has kernel as a dependency. Can't have it both ways
(as someone else here pointed out) because you'd have a circular
dependency...kernel requires glx, but glx requires kernel which requires
glx...and around we go.

As for more USE flags? I would say not a good idea. There are too many of
them already. :)

As for modularity, there comes a time when this goes to an extreme. Adding
closed source libraries (glx) to install along with the kernel source adds
no overhead (one user said 14 seconds to install glx) and provides a
complete solution without compromising any other part of any other
kernel's installation. So users who update a kernel won't be harmed and
everything can coexist. Unmerge will uninstall from the current kernel
path.

I _do_ see the argument that including the extra applications could be
spun off from the main package.

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2005-12-28 18:45 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 ` [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   ` Peter [this message]
2005-12-28 23:54     ` [gentoo-dev] " 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=pan.2005.12.28.18.40.33.680027@comcast.net \
    --to=pete4abw@comcast.net \
    --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