Bug 273312

Summary:	x11/nvidia-driver*: description needs update
Product:	Ports & Packages	Reporter:	Graham Perrin <grahamperrin>
Component:	Individual Port(s)	Assignee:	Alexey Dokuchaev <danfe>
Status:	Open ---
Severity:	Affects Only Me	CC:	ashafer, danfe, fernape
Priority:	---	Keywords:	needs-patch
Version:	Latest	Flags:	grahamperrin: maintainer-feedback? (danfe)
Hardware:	Any
OS:	Any
See Also:	https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273311

Description Graham Perrin 2023-08-23 16:18:42 UTC

<https://www.freshports.org/x11/nvidia-driver-304/#description>
<https://www.freshports.org/x11/nvidia-driver-340/#description>
<https://www.freshports.org/x11/nvidia-driver-390/#description>
<https://www.freshports.org/x11/nvidia-driver-470/#description>
<https://www.freshports.org/x11/nvidia-driver/#description>

Comment 1 Fernando Apesteguía freebsd_committer

2023-08-25 13:01:21 UTC

Thanks for the report Graham,

The tool tip help in bugzilla states the Summary is a short sentence that succinctly describes what the bug is about.

Would it be possible for this and other ports to be more aligned with that?

Having a long summary and  nonexistent description is the opposite of what the PR should look like.

Also it might be nice for the assignee to provide in the description context about the bug, instead of throwing just some links.

Thanks!

Comment 2 Graham Perrin 2023-08-25 17:36:28 UTC

(In reply to Fernando Apesteguía from comment #1)

Feel free to edit, although please note that I often necessarily browse lists of bugs that are _very_ long, so I have an aversion to summary lines that are too short (or nondescript, or outdated). 

Thanks

Comment 3 Fernando Apesteguía freebsd_committer

2023-08-26 11:54:59 UTC

The five packages need to update their descriptionts to distinguish them from the graphics/nvidia-drm-kmod family.

Comment 4 Graham Perrin 2023-08-26 12:33:39 UTC

(In reply to Fernando Apesteguía from comment #3)

Thanks.

Re: the linked bug

Conversation in my fork of the doc tree leads me to suspect that this bug 273312 may be invalid. I'll follow up here in due course.