FS#19504 - makepkg doesn't like "provided" dependencies when checking

Attached to Project: Pacman
Opened by Jasper St. Pierre (magcius) - Tuesday, 18 May 2010, 08:51 GMT
Last edited by Dan McGee (toofishes) - Tuesday, 18 May 2010, 13:30 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 3.3.3
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I was trying to build xorg-server, when I have an nVidia card, so I have
the nvidia and nvidia-utils packages instead of Mesa libgl, since nvidia
supplies their own libGL and libGLX.

Unfortunately, makepkg was unable to build, saying that I needed libgl,
when the nvidia-utils package already provided it.
This task depends upon

Closed by  Dan McGee (toofishes)
Tuesday, 18 May 2010, 13:30 GMT
Reason for closing:  Won't fix
Additional comments about closing:  Working as intended.
Comment by Xavier (shining) - Tuesday, 18 May 2010, 09:37 GMT
xorg-server does not require libgl, it requires libgl >= 7.7 (xorg 1.7) or 7.8 (xorg 1.8).
It's not a bug of makepkg/pacman, it's a feature.
Are you sure nvidia provide that ? And I thought nvidia was not even compatible with latest xorg server (1.8).

Since you're building, you can just remove the versioned makedepend and see if it explodes.
Comment by Jasper St. Pierre (magcius) - Tuesday, 18 May 2010, 10:03 GMT
So is it a bug with nvidia packaging? nvidia-utils provides libgl,
but doesn't specify a version..

Anyway, if a package provides a thing but doesn't provide a version,
is it good for anything? I mean, I don't even think
"requires libgl > 0.0" will pass. That strikes to me odd in a way,
and I'm not sure if that's a "feature"
Comment by Xavier (shining) - Tuesday, 18 May 2010, 10:08 GMT
If you see how to match nvidia (195.36.15) and libgl (7.7.1) versioning, let us know.

And I have no idea whether it's safe to build xorg-server against nvidia libgl.
Comment by Dan McGee (toofishes) - Tuesday, 18 May 2010, 13:30 GMT
This is not a bug as Xavier said- if someone introduces a versioned dependency than your provision needs to be versioned too.

Loading...