On 09 Mar 2009 10:21:05 -0500, Jonathan Kotta wrote: > > I use Ubuntu, and use `make deb-inplace` to build fvwm .debs. Nothing > in my system needs libgtk1.x, and I can imagine many people could say > the same. Should fvwm get rid of this dependency?
This question is actually two. Whether we should have FvwmGtk (I think, yes). And whether libgtk1 should be forced for deb generation (I think, no, it should ideally be synced with ./configure detection). > --- fvwm-2.5.27-old/debian/control.in 2007-08-07 15:17:42.000000000 -0500 > +++ fvwm-2.5.27/debian/control.in 2009-03-09 10:05:07.000000000 -0500 > @@ -3,7 +3,7 @@ > Priority: optional > Maintainer: Fvwm Workers <@FVWMWORKERSLIST@> > Build-Depends: debhelper (>>4.0.0), file, autotools-dev, xlibs-dev, > - libgtk1.2-dev || libgtk1.4-dev, libncurses5-dev, libreadline5-dev, > + libncurses5-dev, libreadline5-dev, > libpng3-dev, libimlib2-dev, gdk-imlib1-dev | gdk-imlib-dev, > libstroke0-dev, libfribidi-dev, libxft-dev, libfreetype6-dev, > librsvg2-dev (>= 2.13.92), libxcursor-dev Well, if you drop libgtk1.*-dev, then you may as well drop gdk-imlib*-dev that is also used in FvwmGtk only. And possibly libimlib2-dev too. I have no deb system at hand to verify. Possibly there should be no library dependancies in Build-Depends at all, just like the rpm procedure does not list them. The whole idea is for the users to be able to build their own custom rpm or deb packages as an alternative to "make install". Suppose we drop all lib*-dev here (or move them to Build-Suggests). I would like you to confirm that this does the intended. I.e. if a user has libgtk1.4 and imlib, then working FvwmGtk is included in the generated deb, otherwise not included, and if he has libpng then fvwm in this deb is built with this support and all corresponding deb dependencies are automatically set. Regards, Mikhael.
