FS#43135 - wine_gecko should not have a direct dependency on wine

Attached to Project: Community Packages
Opened by Alexandre Demers (oxalin) - Tuesday, 16 December 2014, 23:49 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 17 December 2014, 00:40 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
As it is, wine_gecko depends on wine of a specific version or greater. However, this prevents from using it with any package replacing the official wine.

Additional info:
* version 2.34

Even though wine_gecko doesn't do anything by itself, it is an optional dependency of wine and can be left by itself without any problem. In fact, it should be handled the same way as wine-mono. Is there really a need for wine to be of a specific version to use the latest wine_gecko? If there is a need, then this bug will have to be redirect toward the wine-d3dstream-git package.

Steps to reproduce:
* Install wine and wine_gecko
* Install wine-d3dstream-git

* You will be asked to replace wine by wine-d3dstream-git, but it will fail because of the dependency.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Wednesday, 17 December 2014, 00:40 GMT
Reason for closing:  Not a bug
Comment by Doug Newgard (Scimmia) - Wednesday, 17 December 2014, 00:39 GMT
You already proposed the correct solution in the AUR comments, this isn't a repo packaging problem.

Loading...