Bug 335658

Summary: fvwm2 now requires gnome
Product: [openSUSE] openSUSE 11.0 Reporter: Steffen Winterfeldt <snwint>
Component: InstallationAssignee: Ladislav Michnovic <lmichnovic>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Blocker    
Priority: P5 - None CC: coolo, dmacvicar, mmarek, smshUA
Version: Alpha 2   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Steffen Winterfeldt 2007-10-22 13:59:04 UTC 
... or at least nearly.

"FVWM is intended to have a small memory footprint" -- fvwm package
description.

I guess it was this:

* Tue Sep 25 2007 - lmichnovic@suse.cz
- added gnome-libs-devel (/usr/bin/gnome-config) and librsvg into
  BuildReq to enable more features

While it's nice to see that fvwm can now print non-ascii chars in
window titles, it also means that it requires several MB of (gnome-) libs
now.

Currently we are using fvwm2 as WM for YaST during installation. With this
change the inst-sys grows about 1.5MB (compressed!) only to satisfy the
new fvwm lib dependencies.

The options I see are

a) revert that change
b) use another window manager for YaST
Comment 1 Ladislav Michnovic 2007-10-22 14:02:45 UTC 
I can revert the changes immediately. Or do we want to use any other window manager?
Comment 2 Steffen Winterfeldt 2007-10-22 14:16:15 UTC 
I don't know. Switching the WM will cause some work in the YaST area.
OTOH I'm not a fvwm user, so I can't say how much the new features are wanted
there.

In any case there's no need to revert the change immediately. But we should
somehow resolve this until 11.0 as the inst-sys blew up quite considerably
(without any visible benefit).

Adding Duncan for the YaST part.
Comment 3 Ladislav Michnovic 2007-10-22 14:54:11 UTC 
The most dependencies come because of librsvg:
libcairo.so.2
libdl.so.2
libgdk_pixbuf-2.0.so.0 
libglib-2.0.so.0 
libgmodule-2.0.so.0
libgobject-2.0.so.0
librsvg-2.so.2
Comment 4 Steffen Winterfeldt 2007-10-22 15:08:03 UTC 
here's the list I had to add:

  cairo:
    /usr/lib*/libcairo.so.*
  glib2:
    /usr/lib*/libgmodule-2.0.so.*
    /usr/lib*/libgthread-2.0.so.*
  gtk2:
    /usr/lib*/libgdk_pixbuf-2.0.so.*
  librsvg:
    /usr/lib*/librsvg-2.so.*
  pango:
    /usr/lib*/libpango-1.0.so.*
    /usr/lib*/libpangocairo-1.0.so.*
    /usr/lib*/libpangoft2-1.0.so.*
  xorg-x11-libs:
    /usr/lib*/libxcb-render-util.so.*
  xorg-x11-libxcb:
    /usr/lib*/libxcb-render.so.*
  glitz:
    /usr/lib*/libglitz.so.*
  gnome-vfs2:
    /usr/lib*/libgnomevfs-2.so.*
  orbit2:
    /usr/lib*/libORBit-2.so.*
  libcroco-0_6-3:
    /usr/lib*/libcroco-0.6.so.*
  gconf2:
    /usr/lib*/libgconf-2.so.*
  libgsf-1-114:
    /usr/lib*/libgsf-1.so.*
  libavahi-client3:
    /usr/lib*/libavahi-client.so.*
  libavahi-common3:
    /usr/lib*/libavahi-common.so.*
  libavahi-glib1:
    /usr/lib*/libavahi-glib.so.*
Comment 5 Ladislav Michnovic 2007-10-22 15:21:33 UTC 
gnome-libs-devel in BuildReq brings dependencies only into fvwm-gtk which was split off:
libart_lgpl.so.2()(64bit) 
libasound.so.2()(64bit) 
libaudiofile.so.0()(64bit) 
libdb.so.2()(64bit) 
libesd.so.0()(64bit) 
libgnome.so.32()(64bit) 
libgnomesupport.so.0()(64bit) 
libgnomeui.so.32()(64bit) 

So the question is: drop the SVG support in fvwm or choose a different WM for installation?
Comment 6 Stephan Kulow 2007-10-22 15:31:17 UTC 
I would revert. Seriously: if fvwm users would prefer a modern and blown window manager, they would have switched long ago. Or compile fvwm twice, but we already have more than enough window managers in the distro.
Comment 7 Ladislav Michnovic 2007-10-23 09:09:34 UTC 
O.K. then. I have submitted the fvwm without librsvg support.
Comment 8 Ladislav Michnovic 2008-01-17 13:10:16 UTC 
*** Bug 353547 has been marked as a duplicate of this bug. ***