279042 – nvidia-drivers should install module configuration as nvidia.conf

Bug 279042 - nvidia-drivers should install module configuration as nvidia.conf

Summary: nvidia-drivers should install module configuration as nvidia.conf

Status:	RESOLVED WONTFIX

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	New packages (show other bugs)
Hardware:	All Linux

Importance:	High minor
Assignee:	Doug Goldstein (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2009-07-25 12:47 UTC by Jan Vansteenkiste
Modified:	2009-07-30 10:24 UTC (History)
CC List:	3 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Jan Vansteenkiste 2009-07-25 12:47:29 UTC

Since it seems we are moving towards a system of having all module configiration files as /etc/modprobe.d/*.conf, nvidia-drivers should also start doing so. 

Reproducible: Always

Comment 1 Doug Goldstein (RETIRED) gentoo-dev

2009-07-28 02:33:38 UTC

Can you be specific? The following versions had this already fixed...

  nvidia-drivers-71.86.06.ebuild, nvidia-drivers-71.86.07.ebuild,
  nvidia-drivers-71.86.08.ebuild, nvidia-drivers-71.86.09.ebuild,
  nvidia-drivers-96.43.07.ebuild, nvidia-drivers-96.43.09.ebuild,
  nvidia-drivers-96.43.10.ebuild, nvidia-drivers-96.43.11.ebuild,
  nvidia-drivers-100.14.19.ebuild, nvidia-drivers-173.14.09.ebuild,
  nvidia-drivers-173.14.12.ebuild, nvidia-drivers-173.14.15.ebuild,
  nvidia-drivers-173.14.16.ebuild, nvidia-drivers-173.14.17.ebuild,
  nvidia-drivers-173.14.18.ebuild, nvidia-drivers-177.80.ebuild,
  nvidia-drivers-177.82.ebuild, nvidia-drivers-180.22.ebuild,
  nvidia-drivers-180.27.ebuild, nvidia-drivers-180.29.ebuild,
  nvidia-drivers-180.37.ebuild, nvidia-drivers-180.41.ebuild,
  nvidia-drivers-180.44.ebuild, nvidia-drivers-180.51.ebuild:

Comment 2 Jan Vansteenkiste 2009-07-30 10:24:44 UTC

(In reply to comment #1)
> Can you be specific? The following versions had this already fixed...
> 
>   nvidia-drivers-71.86.06.ebuild, nvidia-drivers-71.86.07.ebuild,
>   nvidia-drivers-71.86.08.ebuild, nvidia-drivers-71.86.09.ebuild,
>   nvidia-drivers-96.43.07.ebuild, nvidia-drivers-96.43.09.ebuild,
>   nvidia-drivers-96.43.10.ebuild, nvidia-drivers-96.43.11.ebuild,
>   nvidia-drivers-100.14.19.ebuild, nvidia-drivers-173.14.09.ebuild,
>   nvidia-drivers-173.14.12.ebuild, nvidia-drivers-173.14.15.ebuild,
>   nvidia-drivers-173.14.16.ebuild, nvidia-drivers-173.14.17.ebuild,
>   nvidia-drivers-173.14.18.ebuild, nvidia-drivers-177.80.ebuild,
>   nvidia-drivers-177.82.ebuild, nvidia-drivers-180.22.ebuild,
>   nvidia-drivers-180.27.ebuild, nvidia-drivers-180.29.ebuild,
>   nvidia-drivers-180.37.ebuild, nvidia-drivers-180.41.ebuild,
>   nvidia-drivers-180.44.ebuild, nvidia-drivers-180.51.ebuild:
> 

In that case, sorry for the inconvenience.

I failed to notice they came from a overlay... *SHAME*