FS#41333 - [libva-vdpau-driver] demote libva to a makedep
Attached to Project:
Arch Linux
Opened by Emil (xexaxo) - Thursday, 24 July 2014, 21:10 GMT
Last edited by Maxime Gauduin (Alucryd) - Sunday, 06 December 2020, 09:57 GMT
Opened by Emil (xexaxo) - Thursday, 24 July 2014, 21:10 GMT
Last edited by Maxime Gauduin (Alucryd) - Sunday, 06 December 2020, 09:57 GMT
|
Details
Description:
This package is a vdpau based libva backend. As such it never links/calls back to its loader (libva). Can we demote the libva the dependency to makedep ? As an added bonus we'll remove the circular dependency (libva correctly optdep on this package). Cheers Emil |
This task depends upon
Closed by Maxime Gauduin (Alucryd)
Sunday, 06 December 2020, 09:57 GMT
Reason for closing: Implemented
Additional comments about closing: 0.7.4-5
Sunday, 06 December 2020, 09:57 GMT
Reason for closing: Implemented
Additional comments about closing: 0.7.4-5
Or perhaps I'm day dreaming ?
-Emil
Perhaps there isn't an common ground amongst Arch developers on the topic. IMHO the libreoffice is the preferred approach but if you feel against it I would not object :)
Cheers
-Emil
How about
- phonon-qt4
Requires: phonon-qt4-backend
Provided by: phonon-qt4-vlc/phonon-qt4-gstreamer
or perhaps
- apitrace,mpv,sdl2,dosbox...
Requires: libgl
Provided by: mesa-libgl/nvidia-libgl
Afaict the following approach will preserve the sanity check and addresses my concerns.
package: libva
depends: libva-backend
package: libva-vdpau-driver
provides: libva-backend
Cheers,
Emil
on the loader lib? That way the dependency seems fine to me here.
You know that application/package X has optional support for VAAPI as the said package already has it listed. Thus one should really be installing the actual dependency - libva.
Afaict some packages in Arch follow this approach while others, go in the inverse direction. IMHO the former provides clearer link between the components, while the latter is somewhat confusing from dependency POV.
Although yes, I have to agree with you - proposed solution might be a bit picky, depending on one's current state of mind. Ideally we'll have something like the Debian's "Suggests" tag/section, where the backend will list the frontend/loader.
What do you think, does it make sense ?
I can prepare some patches if people prefer.