Bug 148303

Summary:	Annoyance in python-gnome-extras
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Jonathan Arsenault <jonharson>
Component:	GNOME	Assignee:	Stanislav Brabec <sbrabec>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	andreas.hanke
Version:	Final
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Development	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Jonathan Arsenault 2006-02-06 01:28:08 UTC

This file /usr/lib/python2.4/site-packages/gtk-2.0/totem/plparser.so is include in python-gnome-extras making it really annoying too compille anything depending on it even with all relevent repositorie in my y2pmbuild i still get broken depedency. That thing is a python parser for totem should be seperated in python-totem or python-gnome-totem or something of the like. only thing i really needed in extra is for the gtkhtml module, all the other dep arent half bad beside this totem thingy (why the hell would i need to make a chm viewer depend on totem). Tried too found a work around and made the spec ignore that depedency but doesnt seem doable (yaloki confirmed this can't be done that way), just for the record rpm i was trying to package is gnochm.

Comment 1 Jonathan Arsenault 2006-03-01 13:11:00 UTC

Thats really annoying as even trying too add totem to the buildrequire even if it contain the built i still get failled depedency due too this weird rewuire of python-gnome-extra

Comment 2 Andreas Hanke 2006-03-15 22:40:52 UTC

You mean the bug is that python-gnome-extras depends on totem?

If so, this could be fixed by

- splitting /opt/gnome/lib/libtotem-plparser.so from totem into a subpackage (maybe call it totem-libs), or

- splitting /usr/lib/python2.4/site-packages/gtk-2.0/totem/plparser.so from python-gnome-extras into a subpackage (maybe call it python-gnome-extras-totem)

Comment 3 Andreas Hanke 2006-03-15 22:52:20 UTC

BTW, the former approach (splitting the plparser from totem into a subpackage) sounds more reasonable to me because we already have totem-devel and the plparser might be used by more other applications in the future. Furthermore, having a -libs subpackage where there is already a -devel subpackage sounds intuitive.

Comment 4 Jonathan Arsenault 2006-07-01 13:43:43 UTC

meant to close this