Bug 198969

Summary:	Wine dependencies... pretty much all packages.
Product:	[Fedora] Fedora	Reporter:	Gian Paolo Mureddu <gmureddu>
Component:	wine	Assignee:	Andreas Bierfert <andreas.bierfert>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5	CC:	extras-qa
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-07-18 09:08:14 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 Gian Paolo Mureddu 2006-07-15 04:42:40 UTC

Description of problem:
Updating to either wine-0.9.16 or 0.9.17 results in installation of pretty much
all other wine packages added as dependencies. Attempting to install wine-0.9.17
only will result in additional packages as dependencies, pretty much every other
package with the exception of wine-arts, the follwing will be added deps for the
 wine package:wine-nas-0.9.17-1.fc5
wine-twain-0.9.17-1.fc5
wine-cms-0.9.17-1.fc5
wine-core-0.9.17-1.fc5
wine-capi-0.9.17-1.fc5
wine-jack-0.9.17-1.fc5
wine-esd-0.9.17-1.fc5
wine-ldap-0.9.17-1.fc5

Version-Release number of selected component (if applicable):
0.9.16 and 0.9.17

How reproducible:
Always

Steps to Reproduce:
1. If you have wine installed, remove it.
2. Launch pirut and try to install only the package wine-0.9.17
3. All the other packages will be marked as dependencies.
  
Actual results:
The other packages are added as dependencies when only the wine package is set
to be installed.

Expected results:
If the package was split into several other packages, one expects that these are
optional and you wouldn't require them to run the main package, as it wouldn't
make sense to have several packages to install a single packate, instead of
having that package as one monolithic one.

Additional info:
I have not looked into it yet, but I'd suspect that the Requires declarations of
the .spec should be cleaned up.

Comment 1 Andreas Bierfert 2006-07-18 09:08:14 UTC

The package is just fine. Please _read_ the description: (rpm -qi wine)
[...]
In Fedora Extras wine is actually a meta-package which will install everything
you need for wine to work smoothly. If you don't want to install everything
take a look at the wine-* packages.

So if you don't want the dependencies just don't install the meta package for
the dependencies.

Comment 2 Gian Paolo Mureddu 2006-07-18 09:20:35 UTC

It actually came as a surprise, as when I installed wine, I got to choose the
packages I wanted in Pirut. Then all of a sudden in an update, it added all the
dependencies and installed them. My guess is that the actual wine (as referenced
before) package is wine-core, so only wine-core is really needed, and the other
files provide their descriptive functionality (jack, ldap, cms, esd, etc). The
fact that from one update to the next this was the behavior is what made me post
this as a bug, but I guess there was no easy way to bosolet the previous one.

Thanks for the clarification, though.

Comment 3 Andreas Bierfert 2006-07-18 09:26:37 UTC

No problem and I am sorry that it went this way for you. I tested it here
locally a lot and it worked not pulling in the 'new' wine.

Comment 4 Gian Paolo Mureddu 2006-07-18 09:29:16 UTC

At least I know now how to install it again for when 0.9.18 is released. Thanks
again for your reply, most appreciated.