Future plans : 0.9.2-final and KDE4 port...

[Gilles Caulier-4]

Angelo,

Have you read my previous mail in this thread.

I have fixed in svn a macro in Makefile.am of libkdcraw and the insertCatalog is not add at the right place into libs source code to use i18n files...

I'm waiting a respo,se from Achim about insertCatalog before to fix libkdcraw into svn...

So the tarballs need to be rebuild (:=)))

Gilles

2007/6/13, Angelo Naselli < [hidden email]>:

Alle mercoledì 13 giugno 2007, Achim Bohnet ha scritto:

> On Tuesday, 12. June 2007, Gerhard Kulzer wrote:
> > Am Tuesday 12 June 2007 schrieb Angelo Naselli:
> > > Alle lunedì 11 giugno 2007, Gilles Caulier ha scritto:
> > > > Hi all,
> > > >
> > > > See below the future digiKam plans :
> > > >
> > > > DIGIKAM 0.9.2 FINAL RELEASE:
> > > > ---------------------------------------------
> > > >
> > > > The 0.9.2-final release date is near. Like Gerhard will back at home
> > > > today (:=))), final release will be done at soon.
> > > >
> > > > Gerhard, just a little tip : the libkdcraw need to be released again
> > > > following #146464 B.K.O file. the library have been patched to fix this
> > > > bug. So 0.9.2-final will need a new small 0.1.1 release of libkdcraw...
> > > >
> > > > Angelo, Achim : Please take a care to provide a new package of this
> > > > library for Mandriva and Debian at the same time than digiKam 0.9.2.
> > > > thanks in advance...
> > >
> > > hmm, the problem is that often i see that digikam has been released and
> > > then i know it. Maybe in a case like this one we can talk, also in private,
> > > to get the related libraries released first ;)
> > >
> > > Ok, if you can wait for a day more, tonight i can release new libkdcraw
> > > tonight and maybe a kipi-plugins rc1(?) beta2(?), I would have liked the
> > > rc1 to get final ready for the next week, but i haven't got the time to see
> > > the state of bugs by now, and it depends on docs status anyway....
> > >
> > > Is it ok for you?
> > >
> > > Angelo
> >
> > Can you give me a release hour for libkdcraw tomorrow? Then I can sync 0.9.2
> > final with it.
>
> Hi Gerhard,
>
> Angelo and me tried to get the tarball ready but did not finish.
>
> The problems were/are:
>
>  1) kdcraw binary needs to be installed into $prefix/lib/libkdcraw<abi-major>/kdcraw
>    so libkdcraw0 and libkdraw1 can be installed in parallel  (fixed with commit:
>    674731)  See also: http://www.pathname.com/fhs/pub/fhs-2.3.html#USRLIBLIBRARIESFORPROGRAMMINGANDPA
>
>  2) libkdcraw.mo files need to be installed as libkdcraw<abi-major>.mo. Again to
>    allow libkdcraw0 and libkdraw1 installations at the same time.
>
>    @Gilles: how are the translations loaded?  There no insertCatalog like in the
>    old libkexif lib.
>
>  3) release_*.rb needs to be adpated to the new layout in svn
>
> Angelo and me will try to finish 2) and 3) Wednesday night.  Keep your fingers
> crossed.

>

> Sorry for the delay,
> Achim
> >
> > Gerhard
> >
> >
>
> Index: libkdcraw/dcraw/Makefile.am
> ===================================================================
> --- libkdcraw/dcraw/Makefile.am (revision 674730)
> +++ libkdcraw/dcraw/Makefile.am (revision 674731)
> @@ -14,9 +14,11 @@
>  # Note: dcraw project page is http://cybercom.net/~dcoffin
>
>  bin_PROGRAMS = kdcraw
> +bindir = $(KDCRAW_DIR)
>
> -# The manual page of binary program.
> -man_MANS = kdcraw.1
> +# The manual page of binary program. (Don't install manpage of a library
> +# internal helper app
> +#man_MANS = kdcraw.1
>
>  # This line is require to prevent broken compilation with -std=iso9899:1990 gcc option.
>  # In fact, dcraw.c use lcms.h witch use the "inline" keyword witch do not exist in pure C
> Index: libkdcraw/libkdcraw/dcrawbinary.cpp
> ===================================================================
> --- libkdcraw/libkdcraw/dcrawbinary.cpp (revision 674730)
> +++ libkdcraw/libkdcraw/dcrawbinary.cpp (revision 674731)
> @@ -108,7 +108,7 @@
>
>  const char *DcrawBinary::path()
>  {
> -    return "kdcraw";
> +    return KDCRAW_DIR "/kdcraw";
>  }
>
>  bool DcrawBinary::isAvailable() const
> Index: libkdcraw/libkdcraw/Makefile.am
> ===================================================================
> --- libkdcraw/libkdcraw/Makefile.am     (revision 674730)
> +++ libkdcraw/libkdcraw/Makefile.am     (revision 674731)
> @@ -1,13 +1,12 @@
>  METASOURCES = AUTO
>
> -INCLUDES= $(all_includes)
> +INCLUDES= -DKDCRAW_DIR='"$(KDCRAW_DIR)"' $(all_includes)
>
>  lib_LTLIBRARIES = libkdcraw.la
>
>  libkdcraw_la_SOURCES = dcrawbinary.cpp kdcraw.cpp dcrawsettingswidget.cpp
>
> -libkdcraw_version_info = 0:1:0
> -libkdcraw_la_LDFLAGS = $(all_libraries) $(KDE_RPATH) -version-info $(libkdcraw_version_info) -no-undefined
> +libkdcraw_la_LDFLAGS = $(all_libraries) $(KDE_RPATH) -version-info $(VERSION_INFO) -no-undefined
>  libkdcraw_la_LIBADD  = $(LIB_KDEUI) $(LIB_KDECORE) $(LIB_QT)
>
>  libkdcrawinclude_HEADERS = rawdecodingsettings.h kdcraw.h dcrawbinary.h dcrawsettingswidget.h \
> Index: libkdcraw/configure.in.in
> ===================================================================
> --- libkdcraw/configure.in.in   (revision 674730)
> +++ libkdcraw/configure.in.in   (revision 674731)
> @@ -1,7 +1,20 @@
>  AC_ARG_VAR(PKGCONFIGFOUND, [Path to pkg-config])
>  AC_CHECK_PROG(PKGCONFIGFOUND, pkg-config,[yes])
>
> +#-----------------------------------------------------------------
> +# Library API version
>  # -----------------------------------------------------------------
> +
> +ABI_MAJOR=1
> +VERSION_INFO="1:0:0"
> +
> +AC_SUBST(ABI_MAJOR)

> +AC_SUBST(VERSION_INFO)

> +
> +KDCRAW_DIR="\$(libdir)/libkdcraw\$(ABI_MAJOR)"stt
> +AC_SUBST(KDCRAW_DIR)
> +
> +# -----------------------------------------------------------------
>  # lcms check
>  # -----------------------------------------------------------------
>
>
>

it seems i've sent my mail only to Achim last night :(
I've uploaded new tarball without localization
http://www.linux.it/~anaselli/kipi-plugins/libkdcraw-0.1.1.tar.bz2
Please test it. I believe we can release a new one with localization
in a couple of days at the latest.

WDYT?
        Angelo

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Alle mercoledì 13 giugno 2007, Gilles Caulier ha scritto:
> Angelo,
>
> Have you read my previous mail in this thread.

yep, my mail was sent this morning at two o'clock though, i've just
rewritten it :)
> I have fixed in svn a macro in Makefile.am of libkdcraw and the
> insertCatalog is not add at the right place into libs source code to use
> i18n files...
Achim saw that yesterday. But as i told you this tarball does not include
localizations, so that is not a problem by now.

Localization *must* be fixed first to be used according to soname, or again
we have filename conflict in binary packages. And that should be fixed as
well. As soon as we fix it we can do a new package that *does not* break
binary compatibility, since it adds only po files :)

> I'm waiting a respo,se from Achim about insertCatalog before to fix
> libkdcraw into svn...
Are you saying that insertCatalog fixes po/so filenames?
 
> So the tarballs need to be rebuild (:=)))
That should be done anyway, but since it is only for localization digikam could
be released i believe and we can release 0.1.2.

Angelo

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

2007/6/13, Angelo Naselli <[hidden email]>:

Alle mercoledì 13 giugno 2007, Gilles Caulier ha scritto:
> Angelo,
>
> Have you read my previous mail in this thread.

yep, my mail was sent this morning at two o'clock though, i've just
rewritten it :)
> I have fixed in svn a macro in Makefile.am of libkdcraw and the
> insertCatalog is not add at the right place into libs source code to use
> i18n files...
Achim saw that yesterday. But as i told you this tarball does not include
localizations, so that is not a problem by now.

Localization *must* be fixed first to be used according to soname, or again
we have filename conflict in binary packages. And that should be fixed as
well. As soon as we fix it we can do a new package that *does not* break
binary compatibility, since it adds only po files :)

> I'm waiting a respo,se from Achim about insertCatalog before to fix
> libkdcraw into svn...
Are you saying that insertCatalog fixes po/so filenames?

Well, not sure.

But something like this must be add to constructor implementations from libkdcraw (dcrawbinary.cpp and dcrawsettingswidget.cpp :

KGlobal::locale()->insertCatalogue("libkdcraw");

The insertCatalog() description is here :

http://api.kde.org/3.5-api/kdelibs-apidocs/kdecore/html/classKLocale.html#f14d084c90a004164fa037458377740e

Gilles 

> So the tarballs need to be rebuild (:=)))
That should be done anyway, but since it is only for localization digikam could
be released i believe and we can release 0.1.2.

But please backport at least this fix :

http://websvn.kde.org/branches/extragear/kde3/libs/libkdcraw/libkdcraw/Makefile.am?r1=674731&r2=674797

Gilles

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Arnd Baecker]

On Wed, 13 Jun 2007, Gilles Caulier wrote:

[...]

> Like libkipi and some plugins are already ported, i recommend to start KDE4
> port in trunk as well and let KDE3. I have not yet tested the plugins ported
> : all compile fine only. To port code can take a while especially about to
> learn new API from QT4 and KDE4. Marcel and me we will trying to provide a
> first KDE4 port of digiKam during this summer... I recommend you to port
> your plugin as weel and wait than a host will be ported to KDE4 to start
> test and add new features...

Just a thought: would it be possible to set up some
absolutely minimal (just load one image specified on
the command line) application using QT4/KDE4 which
would make use  of the new libkipi and the already ported plugins,
so that they could be tested?
This would allow to see any pitfalls (if any ;-) already at this stage
of the conversion and take this into account for other plugins?

Well, I don't no anything about what would be involved, so
this might be just a stupid idea... ;-)

Best, Arnd
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Fabien-5]

Hi Gilles and everybody,

Gilles Caulier wrote:
>
> See below the future digiKam plans :
>
> [...]

Don't you think it's time to use a new version numbering schema ?

I think digiKam has reached its stability point.
For most people, when you see a 0.9.x version, it means the software is
quite close to a stable 1.0 version.
Using version 0.10 let digiKam looks as an immature software that lacks
reliability and features. And I definitively think it's not the case !

Creating a 1.0 version would put digiKam under spotlight and that would
be great...
I also think it's important to clearly separate kde3 versions and kde4
version.

This is why I make the following proposal :

- create a 1.0.0 for the next digiKam version (instead of 0.9.2)
0.9.3 would be 1.0.1

- use 2.0 for kde4 port

> DIGIKAM 0.9.3 RELEASE:
> ------------------------------------
>
> DIGIKAM 0.10.0 RELEASE (KDE4 PORT):
> ---------------------------------------------------------
>
> This is the future : the famous KDE4/Qt4/CMake port....
>
>
> How many time will take KDE4 port ?
>
> Good question : this depand of free time available. There are some
> scripts to use to simplify task, but personally i don't like script
> source code converters (:=))). The code can be completly unreadable and
> this is not the better way to learn the new API.
>
> I think we can plan to have a full port of digiKam for september (2007
> of course)...

As an end user, I think it's too early to migrate to KDE4. I think it
would have been better to do that in around 6 months...
Personaly, I won't migrate to KDE4 before at least 1 year. I'm also
curious to see when distributions will put KDE4 by default. I guess it's
better to have kde4 desktop with some kde3 softs than the contrary, but
maybe I'm wrong ?

But, I fully understand that developpers are willing to migrate very
soon :) And you, developpers, work hard enough to choose whenever to
want to use new kde4, so I won't complain :)

--
Fabien

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

>

> Well, not sure.
>
> But something like this must be add to constructor implementations from
> libkdcraw (dcrawbinary.cpp and dcrawsettingswidget.cpp:
>
> KGlobal::locale()->insertCatalogue("libkdcraw");
>
> The insertCatalog() description is here :
>
> http://api.kde.org/3.5-api/kdelibs-apidocs/kdecore/html/classKLocale.html#f14d084c90a004164fa037458377740e
>
> Gilles
>
> > So the tarballs need to be rebuild (:=)))
> > That should be done anyway, but since it is only for localization digikam
> > could
> > be released i believe and we can release 0.1.2.
>
>
> But please backport at least this fix :
>
> http://websvn.kde.org/branches/extragear/kde3/libs/libkdcraw/libkdcraw/Makefile.am?r1=674731&r2=674797

if Gerhard has no problems i can do that tonight, but

it would be nice to fix localization problem as well. Now that Makefile.am has changed again i have to fix
the prepare script again also for version-info :(

There two things i don't like on Achim's changes (he knows so i can speak :) )
- bindir = $(KDCRAW_DIR)
I don't like bindir to be changed into makefile.am
-  -DKDCRAW_DIR='"$(KDCRAW_DIR)"'
i don't like the way to access the var value.
I would have liked mostly to have an install-hook target maybe with a noinst_PROGRAMS first.
But time was so little to make it working in any cases, so Achim's solution is ok for me. Of course
we must pay attantion not to add programs in that Makefile.am though.

A note, this discussion has been missed in kde-imaging@, I know we're almost all here, but
someone should make a summary for that list when we've finished :)

Angelo



_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

On Wednesday, 13. June 2007, Arnd Baecker wrote:

> On Wed, 13 Jun 2007, Gilles Caulier wrote:
>
> [...]
>
> > Like libkipi and some plugins are already ported, i recommend to start KDE4
> > port in trunk as well and let KDE3. I have not yet tested the plugins ported
> > : all compile fine only. To port code can take a while especially about to
> > learn new API from QT4 and KDE4. Marcel and me we will trying to provide a
> > first KDE4 port of digiKam during this summer... I recommend you to port
> > your plugin as weel and wait than a host will be ported to KDE4 to start
> > test and add new features...
>
> Just a thought: would it be possible to set up some
> absolutely minimal (just load one image specified on
> the command line) application using QT4/KDE4 which
> would make use  of the new libkipi and the already ported plugins,
> so that they could be tested?
> This would allow to see any pitfalls (if any ;-) already at this stage
> of the conversion and take this into account for other plugins?
>
> Well, I don't no anything about what would be involved, so
> this might be just a stupid idea... ;-)

that's a good idea.  I suggested something like this
before ;)

        kipirun <pluginname>  file ...

With some serice desktop files this give a much better
kimg replacement.

Achim
>
> Best, Arnd
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
>
>



--
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- [hidden email]
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

On Wednesday, 13. June 2007, Gilles Caulier wrote:

> 2007/6/13, Gilles Caulier <[hidden email]>:
> >
> >
> >
> > 2007/6/13, Achim Bohnet <[hidden email]>:
> > >
> > > On Tuesday, 12. June 2007, Gerhard Kulzer wrote:
> > > > Am Tuesday 12 June 2007 schrieb Angelo Naselli:
> > > > > Alle lunedì 11 giugno 2007, Gilles Caulier ha scritto:
> > > > > > Hi all,
> > > > > >
> > > > > > See below the future digiKam plans :
> > > > > >
> > > > > > DIGIKAM 0.9.2 FINAL RELEASE:
> > > > > > ---------------------------------------------
> > > > > >
> > > > > > The 0.9.2-final release date is near. Like Gerhard will back at
> > > home
> > > > > > today (:=))), final release will be done at soon.
> > > > > >
> > > > > > Gerhard, just a little tip : the libkdcraw need to be released
> > > again
> > > > > > following #146464 B.K.O file. the library have been patched to fix
> > > this
> > > > > > bug. So 0.9.2-final will need a new small 0.1.1 release of
> > > libkdcraw...
> > > > > >
> > > > > > Angelo, Achim : Please take a care to provide a new package of
> > > this
> > > > > > library for Mandriva and Debian at the same time than digiKam
> > > 0.9.2.
> > > > > > thanks in advance...
> > > > >
> > > > > hmm, the problem is that often i see that digikam has been released
> > > and
> > > > > then i know it. Maybe in a case like this one we can talk, also in
> > > private,
> > > > > to get the related libraries released first ;)
> > > > >
> > > > > Ok, if you can wait for a day more, tonight i can release new
> > > libkdcraw
> > > > > tonight and maybe a kipi-plugins rc1(?) beta2(?), I would have liked
> > > the
> > > > > rc1 to get final ready for the next week, but i haven't got the time
> > > to see
> > > > > the state of bugs by now, and it depends on docs status anyway....
> > > > >
> > > > > Is it ok for you?
> > > > >
> > > > > Angelo
> > > >
> > > > Can you give me a release hour for libkdcraw tomorrow? Then I can sync
> > > 0.9.2
> > > > final with it.
> > >
> > > Hi Gerhard,
> > >
> > > Angelo and me tried to get the tarball ready but did not finish.
> > >
> > > The problems were/are:
> > >
> > > 1) kdcraw binary needs to be installed into
> > > $prefix/lib/libkdcraw<abi-major>/kdcraw
> > >    so libkdcraw0 and libkdraw1 can be installed in parallel  (fixed with
> > > commit:
> > >    674731)  See also:
> > > http://www.pathname.com/fhs/pub/fhs-2.3.html#USRLIBLIBRARIESFORPROGRAMMINGANDPA
> >
> >
> > Achim,
> >
> > in libkdcraw/libkdcraw/Makefile.am, this is not correct to use the macro :

I know.  I've tried libkdcraw_la_CPPFLAGS and suddenly no .moc files
where build anymore.  That's the reason I used INCLUDE as dirty
workaround.

> >
> >
> > INCLUDES = -DKDCRAW_DIR='"$(KDCRAW_DIR)"' $(all_includes)
> >
> > The -DKDCRAW_DIR='"$(KDCRAW_DIR)"' sentence is not at the right place. You
> > must use this macro instead :
> >
> > INCLUDES= $(all_includes)
> > libkdcraw_la_CFLAGS  = INCLUDES= -DKDCRAW_DIR='"$(KDCRAW_DIR)"'
> >
>
> Oups sorry, wrong copy and paste. This is the right sentence :
>
> INCLUDES= $(all_includes)
> libkdcraw_la_CXXFLAGS = -DKDCRAW_DIR='"$(KDCRAW_DIR)"'

%$#!^$^ what wrong here.  Again as with above: no .moc
files build.

FYI:
Gilles suggested on IRC and commited use of KDE_CXXFLAGS
and now it works here too.   Thx again Gilles.

Achim
>
> Compile fine here...
>
> Gilles
>



--
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- [hidden email]
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

On Wednesday, 13. June 2007, Fabien wrote:

> Hi Gilles and everybody,
>
> Gilles Caulier wrote:
> >
> > See below the future digiKam plans :
> >
> > [...]
>
> Don't you think it's time to use a new version numbering schema ?
>
> I think digiKam has reached its stability point.
> For most people, when you see a 0.9.x version, it means the software is
> quite close to a stable 1.0 version.
> Using version 0.10 let digiKam looks as an immature software that lacks
> reliability and features. And I definitively think it's not the case !
>
> Creating a 1.0 version would put digiKam under spotlight and that would
> be great...
> I also think it's important to clearly separate kde3 versions and kde4
> version.
>
> This is why I make the following proposal :
>
> - create a 1.0.0 for the next digiKam version (instead of 0.9.2)
> 0.9.3 would be 1.0.1
>
> - use 2.0 for kde4 port

I like the 1.* -> KDE3,  2.* KDE4 idea too.

Achim

>
>
>
> > DIGIKAM 0.9.3 RELEASE:
> > ------------------------------------
> >
> > DIGIKAM 0.10.0 RELEASE (KDE4 PORT):
> > ---------------------------------------------------------
> >
> > This is the future : the famous KDE4/Qt4/CMake port....
> >
> >
> > How many time will take KDE4 port ?
> >
> > Good question : this depand of free time available. There are some
> > scripts to use to simplify task, but personally i don't like script
> > source code converters (:=))). The code can be completly unreadable and
> > this is not the better way to learn the new API.
> >
> > I think we can plan to have a full port of digiKam for september (2007
> > of course)...
>
> As an end user, I think it's too early to migrate to KDE4. I think it
> would have been better to do that in around 6 months...
> Personaly, I won't migrate to KDE4 before at least 1 year. I'm also
> curious to see when distributions will put KDE4 by default. I guess it's
> better to have kde4 desktop with some kde3 softs than the contrary, but
> maybe I'm wrong ?
>
> But, I fully understand that developpers are willing to migrate very
> soon :) And you, developpers, work hard enough to choose whenever to
> want to use new kde4, so I won't complain :)
>
> --
> Fabien
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
>
>

--
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- [hidden email]
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Dnia środa 13 czerwiec 2007, Fabien napisał:
> This is why I make the following proposal :
>
> - create a 1.0.0 for the next digiKam version (instead of 0.9.2)
> 0.9.3 would be 1.0.1
>
> - use 2.0 for kde4 port

I like it very much. Today 2.0 adds much credibility and sense of
maturity in folks eyes (unfortunately I am not joking).

m.

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel