On Friday 09 March 2007 18:45, Andreas Pakulat wrote:
> On 09.03.07 17:47:25, Alexander Neundorf wrote:
> > On Friday 09 March 2007 13:02, Boyd Stephen Smith Jr. wrote:
> > > On Thursday 08 March 2007 11:36:03 Alexander Neundorf wrote:
> > > > Do you know when SUSE 10.3 and kUbuntu 7.04 Feisty Fawn wil be
> > > > released
> > >
> > > and
> > >
> > > > which versions they will ship ?
> > >
> > > I'm running feisty right now and have 2.4.5-1build1 installed.  My
> > > Gentoo box
> > > at home has 2.4.3 stable and 2.4.6 in testing. Debian has only 2.0.5 in
> > > stable, but etch should be moving to stable "real soon now" and it
> > > currently
> > > has 2.4.4-1.  I'm not sure what level of freeze is in place @ Debian,
> > > but the only outstanding bug against 2.4.5-1 is on hurd-i386 so it
> > > could make it into etch before it becomes stable.
> >
> > 2.4.4 had some serious problems, it shouldn't be in stable. Can you
> > contact somebody from Debian and push a bit that they go for 2.4.5 or
> > 2.4.6 ?
>
> Do you have a link for the problems? Then I could file severe bugreports
> against the etch version. There's no other way to get 2.4.5 into Etch,
> as Debian is in full freeze, which means packages get into Etch only if
> there's an important bug that needs fixing.
>
> I did a quick check on the bug database for cmake but found only 1
> critical bugreport.

http://public.kitware.com/pipermail/cmake/2006-November/012110.html:

1) Fix problem with LIBRARY_OUTPUT_PATH and linking to a dll foo.dll.lib
  instead of foo.lib

This one is probably only for Windows. This might have been the main reason 
why 2.4.5 was released so quickly after 2.4.4.

2) Do not depend on optimized libraries for a debug build and visa versa.

With cmake you can say
target_link_libraries(myapp optimized foolib debug foolib_d)
and then cmake will link to foolib_d when doing a debug build. That's probably 
also true for Linux, which is probably not a killer, but not nice.

3) Fix target name matching custom command output conflict.

This can also be very critical, since it can break the build. 
  
4) Fix FindQt3 so that it does not find qt4

Not nice, but not really a killer.

5) Fix FindKDE4 so that it only looks for kde4-config

Only checking for kde4-config is better.

So due to 1) we (KDE) cannot require 2.4.4 as minimum version, since this is 
broken on Windows. And I guess 3) can also seriously break the build.

Bye
Alex
-- 
Work: alexander.neundorf AT jenoptik.com - http://www.jenoptik-los.de
Home: neundorf AT kde.org                - http://www.kde.org
      alex AT neundorf.net               - http://www.neundorf.net