Subject: Re: kdevelop-20000322
To: Berndt Josef Wulf <wulf@ping.net.au>
From: None <mcmahill@mtl.mit.edu>
List: tech-pkg
Date: 03/25/2000 17:09:20
On Sun, 26 Mar 2000, Berndt Josef Wulf wrote:

> mcmahill@mtl.mit.edu wrote
> > > 
> > > Hmm, would you have time to look at the pkgsrc for KDevelop on
> > > cvs.netbsd.org/~wulf? 
> > > 
> > > What do I need to do? Is it enough to supply the configure arguments
> > > 
> > > --with-qt-include=${X11BASE}/include/qt1 etc.... ?
> > 
> > for most of the kde* pkgs, I had to:
> > 
> > 1) modify the pkg Makefile as you noted
> > 
> > 2) edit the configure script and change
> >     moc -> moc1
> >     -lqt -> -lqt1
> > 
> > for kdevelop I also had to edit
> > pkgsrc/devel/kdevelop/work.i386/kdevelop-1.0/kdevelop/Makefile.in
> > 
> > and change "-lqt" to "-lqt1"
> > 
> > I have to admit that I'm not a KDE user at all.  My only interest is to be
> > able to upgrate Qt since cad/vipec needs the newer Qt.  But I couldn't
> > justify breaking KDE for that.
> 
> This is easy enough to implement, the problem is that in case of
> Kdevelop all project templates using the qt stuff will nolonger work.
> They are all packed up in tar.gz archives and using project templates
> is what make KDevelop so powerful.

oh yuck....

> 
> /usr/X11R6/share/kde/apps/kdevelop/templates/c.tar.gz
> /usr/X11R6/share/kde/apps/kdevelop/templates/cpp.tar.gz
> /usr/X11R6/share/kde/apps/kdevelop/templates/kdemdi.tar.gz
> /usr/X11R6/share/kde/apps/kdevelop/templates/mini.tar.gz
> /usr/X11R6/share/kde/apps/kdevelop/templates/mini2.tar.gz
> /usr/X11R6/share/kde/apps/kdevelop/templates/normal.tar.gz
> /usr/X11R6/share/kde/apps/kdevelop/templates/normal2.tar.gz
> /usr/X11R6/share/kde/apps/kdevelop/templates/normalogl.tar.gz
> /usr/X11R6/share/kde/apps/kdevelop/templates/qextmdi.tar.gz
> /usr/X11R6/share/kde/apps/kdevelop/templates/qt.tar.gz
> /usr/X11R6/share/kde/apps/kdevelop/templates/qt2.tar.gz
> /usr/X11R6/share/kde/apps/kdevelop/templates/qtmdi.tar.gz
> 


> I can't see an easy way of fixing this.
> 
> In hinsight, wouldn't it be easier to call the new qt-2.x stuff
> libqt2 and moc2 and left libqt stuff alone? 

well, the problem is I assume that moving forward that qt-2.x will be the
"standard" and qt-1.x will be obsolete.  KDE2 which is supposed to come
out in a couple of months is supposed to have moved to qt-2.x.


ugh.  just when I though I was almost done.....

-Dan