Bug 211898

Summary: xorg-x11-devel: missing dep on libGL/libGLU
Product: Red Hat Enterprise Linux 4 Reporter: Rex Dieter <rdieter>
Component: xorg-x11Assignee: Adam Jackson <ajax>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4.4CC: xgl-maint
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-04-17 19:23:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Rex Dieter 2006-10-23 19:02:51 UTC
xorg-x11-devel contains the symlinks 
/usr/X11R6/%{_lib}/libGLU.so
%{_libdir}/libGLU.so
but xorg-x11-devel doesn't contain any (direct) dependancy to pull in the target
of that symlink.  The same can be said for libGL, but that get's pulled
indirectly via xorg-x11-libs.

Not sure how best to handle this, but possibilities include:
1.  using file deps: -devel should
Requires: %{_x11libdir}/libGLU.so
Requires: %{_x11libdir}/libGL.so

2.  using explicit pkg deps: -devel should:
Requires: %{name}-Mesa-libGL = %{version]-%{release}
Requires: %{name}-Mesa-libGLU = %{version]-%{release}

3.  using virtual libGL/libGLU dep: -devel should
Requires: libGL.%{_target_cpu} libGLU.%{_target_cpu}
and -Mesa-libGL should
Provides: libGL.%{_target_cpu} = %{libGL_version}
and -Mesa-libGLU should
Provides: libGLU.%{_target_cpu} = %{libGLU_version}

I'd say 1 appears to be simplest/sanest approach.

Comment 1 Matěj Cepl 2007-10-17 08:41:30 UTC
Yes, I can confirm with the currently updated RHEL4 this is true. Sorry, for
letting this slip out of our screen for so long.

Comment 2 Adam Jackson 2012-04-17 19:23:06 UTC
No further non-security updates are planned for xorg-x11 in RHEL4.  If this issue is not addressed in RHEL5 or newer, please update the affected product version and reopen this bug.