Bug 189564

Summary:	wxGTK package not providing virtual wxwin package
Product:	[Fedora] Fedora	Reporter:	Ben Coleman <oloryn>
Component:	wxGTK	Assignee:	Matthew Miller <mattdm>
Status:	CLOSED WONTFIX	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-04-21 15:37:32 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 Ben Coleman 2006-04-21 03:20:28 UTC

Description of problem:

There's a convention that packages of WxWindows ports should provide a (virtual)
package wxwin, so that packages can depend on the presence of a WxWindows port,
regardless of the toolkit used (e.g., see
http://dag.wieers.com/packages/wxGTK/wxGTK.spec).  The FC4 and FC5 Extras
packages don't provide this.

Comment 1 Matthew Miller 2006-04-21 03:35:26 UTC

Hmmm. See comment #5 in bug #154618. That's about "wxWindows" rather than
"wxwin", but I think the same logic applies.....

Comment 2 Ben Coleman 2006-04-21 04:14:56 UTC

In other words, the packages might connect at the package dependency level, but
they're not going to connect at the link level?  If you've built against wxGTK,
it's not going to link against wxqt, because there's a common API at the source
level, but not a common ABI at the link level.  Silly me, I figured if the
convention existed, it would actually work.

Comment 3 Matthew Miller 2006-04-21 15:37:32 UTC

Teh generated libraries are all things like "libwx_gtk2u_core", and so
presumably "libwx_qt_core" or "libwx_motif_core". So I don't think we even need
to test to see that it won't work.....

I'm going to close this as WONTFIX. Reopen if I'm wrong. :)