Bug 249310 - graphics/mesa-demos: avoid conflict with glx-utils
Summary: graphics/mesa-demos: avoid conflict with glx-utils
Status: Closed Not Accepted
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-x11 (Nobody)
URL:
Keywords: patch
: 279826 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-09-14 13:14 UTC by Jan Beich
Modified: 2024-06-18 13:38 UTC (History)
7 users (show)

See Also:
manu: maintainer-feedback-
jbeich: maintainer-feedback? (se)
Alexander88207: maintainer-feedback+
lcook: maintainer-feedback+
portmaster: maintainer-feedback+


Attachments
v1 (6.73 KB, patch)
2020-09-14 13:14 UTC, Jan Beich
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Beich freebsd_committer freebsd_triage 2020-09-14 13:14:32 UTC
Created attachment 217951 [details]
v1

- Add _demo suffix similar to bitmap_demo. Inspired by https://github.com/netbsd/pkgsrc/commit/b3c2d76226ac
- glxinfo has consumers, so switch to glx-utils instead of patching to support glxinfo_demo
Comment 1 Alexander Vereeken freebsd_triage 2020-09-14 13:50:18 UTC
Would then switch to glx-utils then.
Comment 2 Jan Beich freebsd_committer freebsd_triage 2020-12-23 20:22:20 UTC
Ping to x11@. I can switch consumers while keeping CONFLICTS but some users may want other demos e.g., eglinfo, eglgears_x11, glxgears_pixmap.
Comment 3 Emmanuel Vadot freebsd_committer freebsd_triage 2020-12-30 15:08:19 UTC
NAK.
You cannot add a ports that install the same binaries as another one and then changing the name of the binaries of the historical port.
Again doing that kind of stuff without talking to people is very rude.
Never the less I think that depending on mesa-demos for a ports is wrong and instead people should just use the language of their choice to query the opengl info they want. If they really insist for having glxinfo, let them depend on mesa-demos.
Comment 4 Max Brazhnikov freebsd_committer freebsd_triage 2024-06-18 13:38:56 UTC
*** Bug 279826 has been marked as a duplicate of this bug. ***