Bug 206095 - ~app-office/gnumeric-1.8.0 + ~x11-libs/goffice-0.6.1 do not require libgnomeprint/libgnomeprintui
Bug#: 206095 Product:  Gentoo Linux Version: unspecified Platform: All
OS/Version: Linux Status: RESOLVED Severity: trivial Priority: P2
Resolution: FIXED Assigned To: gnome-office@gentoo.org Reported By: dale@dalew.co.uk
Component: Ebuilds
URL: 
Summary: ~app-office/gnumeric-1.8.0 + ~x11-libs/goffice-0.6.1 do not require libgnomeprint/libgnomeprintui
Keywords:  
Status Whiteboard: 
Opened: 2008-01-16 16:43 0000
Description:   Opened: 2008-01-16 16:43 0000
Hi,

I noticed that the ebuild for goffice 0.6.1 has a libgnomeprint dependency, and
the ebuild for gnumeric 1.8.0 has libgnomeprint and libgnomeprintui
dependencies.

Looking at the webpage for gnumeric and the Changelog for goffice, these
dependencies are no longer required (instead they use GtkPrint which is part of
the gtk package).  I have updated the ebuilds so that they do not contain these
dependencies.

Reproducible: Always

Steps to Reproduce:
1.Install gnumeric 1.8.0, it will pull in libgnomeprint/libgnomeprintui.
2.
3.

Actual Results:  
The libs are installed on my system.

Expected Results:  
The libs are not installed on my system.

------- Comment #1 From Dale Whittaker 2008-01-16 16:46:41 0000 -------
Created an attachment (id=141067) [details]
Remove unrequired libgnomeprint dep.

------- Comment #2 From Dale Whittaker 2008-01-16 16:47:22 0000 -------
Created an attachment (id=141068) [details]
Remove unrequired libgnomeprint/libgnomeprintui deps.

------- Comment #3 From Jakub Moc (RETIRED) 2008-01-16 21:57:10 0000 -------
Please use unified diffs instead of attaching huge ebuilds...
bug-wranglers@gentoo.org

------- Comment #4 From Gilles Dartiguelongue 2008-01-16 22:50:30 0000 -------
you are perfectly right, a quick readelf -d greping proved that they are not
even linked to it on a as-needed system. Fixed in tree, thanks for reporting.

------- Comment #5 From Jakub Moc (RETIRED) 2008-01-20 10:58:30 0000 -------
*** Bug 206752 has been marked as a duplicate of this bug. ***