Fwd: Trans.: [exiv2] Exiv2 release 0.13

[Gilles Caulier-4]

I forward this message from Exiv2 ML to digiKam ML for a better visibility to packagers and translators...

 

Gilles

----- Message transféré de Andreas Huggel <[hidden email]> -----
  Date: Sat, 03 Mar 2007 07:44:36 -0000
    De: Andreas Huggel <[hidden email]>
Adresse de [hidden email]
Sujet: [exiv2] Exiv2 release 0.13
     À: [hidden email]

This release features the Native Language Support framework and
partial translations for Finnish, French, German, Polish, Russian and
Spanish. It adds read-support for Fujifilm RAF images and a number of
other features and fixes, listed in the changelog.

Changelog: http://www.exiv2.org/changelog.html
Download : http://www.exiv2.org/download.html

Thanks for all your contributions and support!

Have fun!
Andreas





Yahoo! Groups Links

<*> To visit your group on the web, go to:
   http://uk.groups.yahoo.com/group/exiv2/

<*> Your email settings:
   Individual Email | Traditional

<*> To change settings online go to:
   http://uk.groups.yahoo.com/group/exiv2/join
   (Yahoo! ID required)

<*> To change settings via email:
   mailto:[hidden email]
   mailto:[hidden email]

<*> To unsubscribe from this group, send an email to:
   [hidden email]

<*> Your use of Yahoo! Groups is subject to:
   http://uk.docs.yahoo.com/info/terms.html


----- Fin du message transféré -----


--
Gilles CAULIER
Email :    [hidden email]
Internet : http://caulier.gilles.free.fr

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

Alle 09:33, sabato 3 marzo 2007, Gilles Caulier ha scritto:
> I forward this message from Exiv2 ML to digiKam ML for a better visibility
> to packagers and translators...
>
> Gilles
>
I'm afraid the library visioning is a bit odd, the library built
bcame libexiv2-0.13.so, that means, if I'm not wrong that we miss
the binary compatibility. I would have expected something like
libkexiv2.so.X.Y.Z and X, Y, Z giving the compatibility or not.

Achim, am I wrong?

Angelo

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

[Gerhard Kulzer]

Am Saturday 03 March 2007 schrieb Angelo Naselli:

> Alle 09:33, sabato 3 marzo 2007, Gilles Caulier ha scritto:
> > I forward this message from Exiv2 ML to digiKam ML for a better
> > visibility to packagers and translators...
> >
> > Gilles
>
> I'm afraid the library visioning is a bit odd, the library built
> bcame libexiv2-0.13.so, that means, if I'm not wrong that we miss
> the binary compatibility. I would have expected something like
> libkexiv2.so.X.Y.Z and X, Y, Z giving the compatibility or not.
>
> Achim, am I wrong?
>
> Angelo

I think you are not wrong (=right). Once I had installed 0.13 I had to
recompile kipi-plugins, digikam and it's plugins. So the same goes for the
binaries I guess.

Gerhard

--
Hakuna matata
http://www.gerhard.fr

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

[Gilles Caulier-4]

Angelo, Achim,

 

The Exiv2 library coordinator is in this room (Andreas).

 

Andreas, what do you think about versionning number?

 

Gilles

 

2007/3/4, Gerhard Kulzer <[hidden email]>:

Am Saturday 03 March 2007 schrieb Angelo Naselli:

> Alle 09:33, sabato 3 marzo 2007, Gilles Caulier ha scritto:
> > I forward this message from Exiv2 ML to digiKam ML for a better
> > visibility to packagers and translators...
> >
> > Gilles
>
> I'm afraid the library visioning is a bit odd, the library built
> bcame libexiv2-0.13.so, that means, if I'm not wrong that we miss
> the binary compatibility. I would have expected something like
> libkexiv2.so.X.Y.Z and X, Y, Z giving the compatibility or not.
>
> Achim, am I wrong?
>
> Angelo

I think you are not wrong (=right). Once I had installed 0.13 I had to
recompile kipi-plugins, digikam and it's plugins. So the same goes for the
binaries I guess.

Gerhard

--
Hakuna matata
http://www.gerhard.fr

_______________________________________________
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

On Sunday 04 March 2007 15:14, Gilles Caulier wrote:
> Angelo, Achim,
>
> The Exiv2 library coordinator is in this room (Andreas).
>
> Andreas, what do you think about versionning number?
>
> Gilles

Exiv2 and it's interface are still unstable. Thus the 0.x version number
and the use of the simple library versioning mechanism. The API/ABI
change with every version, although sometimes in subtle ways (which is
worse); the current versioning system makes this very clear. The other
versioning system is only meaningful if API/ABI are reasonably stable.
Exiv2 will get there too.

For an example of a subtle API change see
http://uk.groups.yahoo.com/group/exiv2/message/523

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

Alle 12:32, domenica 4 marzo 2007, Andreas Huggel ha scritto:

> On Sunday 04 March 2007 15:14, Gilles Caulier wrote:
> > Angelo, Achim,
> >
> > The Exiv2 library coordinator is in this room (Andreas).
> >
> > Andreas, what do you think about versionning number?
> >
> > Gilles
>
> Exiv2 and it's interface are still unstable. Thus the 0.x version number
> and the use of the simple library versioning mechanism. The API/ABI
> change with every version, although sometimes in subtle ways (which is
> worse); the current versioning system makes this very clear. The other
> versioning system is only meaningful if API/ABI are reasonably stable.
> Exiv2 will get there too.
>
> For an example of a subtle API change see
> http://uk.groups.yahoo.com/group/exiv2/message/523

I don't fully agree with that, if a bug fixing change the api, or an

api changes you can always break binary compatibility using  -version-info
just increasing the first number and let others (two) to zero.
The right now versioning system is by default a compatibility breaker.
And you can never say from now on i won't break it because you change
the name of the library and who use the old one cannot use the new one
without rebuilding itself.
You can always break binary compatibility using also  -release X.Y
IMO libtools is quite clear.

Angelo

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

[Gilles Caulier-4]

Nota : Andreas, to improve the binary compatibilty, we can use a d private internal class everywhere to contain all private members.

 

Like this, if you add a new private member in a class the benary is not broken because private member declarations are include in cpp files not in hpp.

 

This way increase the compilation time too... When the API will be more stable for you, i can patch the library like this. I know very well this technic since i have patched all digiKam core implementation. Also, libkexiv2 and libkdcraw are implemented using d private class.

 

Friendly

 

Gilles 

 

2007/3/4, Angelo Naselli <[hidden email]>:

Alle 12:32, domenica 4 marzo 2007, Andreas Huggel ha scritto:

> On Sunday 04 March 2007 15:14, Gilles Caulier wrote:
> > Angelo, Achim,
> >
> > The Exiv2 library coordinator is in this room (Andreas).
> >
> > Andreas, what do you think about versionning number?
> >
> > Gilles
>
> Exiv2 and it's interface are still unstable. Thus the 0.x version number
> and the use of the simple library versioning mechanism. The API/ABI
> change with every version, although sometimes in subtle ways (which is
> worse); the current versioning system makes this very clear. The other
> versioning system is only meaningful if API/ABI are reasonably stable.
> Exiv2 will get there too.
>
> For an example of a subtle API change see
> http://uk.groups.yahoo.com/group/exiv2/message/523

I don't fully agree with that, if a bug fixing change the api, or an
api changes you can always break binary compatibility using  -version-info
just increasing the first number and let others (two) to zero.
The right now versioning system is by default a compatibility breaker.
And you can never say from now on i won't break it because you change
the name of the library and who use the old one cannot use the new one
without rebuilding itself.
You can always break binary compatibility using also  -release X.Y
IMO libtools is quite clear.

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

> Also, libkexiv2
well we can talk about that either :p
imo it should have named libkexiv, what are you going to do
once libexiv2 become libexiv3?
From applications point of you a front end could be indipendent
by that.

Angelo

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

Alle 09:33, sabato 3 marzo 2007, Gilles Caulier ha scritto:
> I forward this message from Exiv2 ML to digiKam ML for a better visibility
> to packagers and translators...
>
> Gilles
>

>
> ----- Message transféré de Andreas Huggel <[hidden email]> -----
>   Date: Sat, 03 Mar 2007 07:44:36 -0000
>     De: Andreas Huggel <[hidden email]>
> Adresse de retour:[hidden email]
> Sujet: [exiv2] Exiv2 release 0.13
>      À: [hidden email]
>
> This release features the Native Language Support framework and
> partial translations for Finnish, French, German, Polish, Russian and
> Spanish. It adds read-support for Fujifilm RAF images and a number of

Other little issue is about translations, why call the files Exiv2?

all the applications take the same filename as the executable or package
name, I would have expected exiv2 instead...

I'm not against it, this mine is only to say that packaging exiv2 is
not easy and need some attentions :)

Angelo

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

[Gilles Caulier-4]

Angelo, there is a main binary program to handle metadata by command line, like Exiftool work... This program is named exiv2.

 

Gilles

 

2007/3/4, Angelo Naselli <[hidden email]>:

Alle 09:33, sabato 3 marzo 2007, Gilles Caulier ha scritto:
> I forward this message from Exiv2 ML to digiKam ML for a better visibility
> to packagers and translators...
>
> Gilles
>

>
> ----- Message transféré de Andreas Huggel <[hidden email]> -----
>   Date: Sat, 03 Mar 2007 07:44:36 -0000
>     De: Andreas Huggel <[hidden email]>
> Adresse de [hidden email]
> Sujet: [exiv2] Exiv2 release 0.13
>      À: [hidden email]
>
> This release features the Native Language Support framework and
> partial translations for Finnish, French, German, Polish, Russian and
> Spanish. It adds read-support for Fujifilm RAF images and a number of

Other little issue is about translations, why call the files Exiv2?
all the applications take the same filename as the executable or package
name, I would have expected exiv2 instead...

I'm not against it, this mine is only to say that packaging exiv2 is
not easy and need some attentions :)

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

[Gilles Caulier-4]

Exiv2 to Exiv3 ??? Really Andreas ?

 

Gilles

 

2007/3/4, Angelo Naselli <[hidden email]>:

> Also, libkexiv2
well we can talk about that either :p
imo it should have named libkexiv, what are you going to do
once libexiv2 become libexiv3?
From applications point of you a front end could be indipendent
by that.

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 18:50, domenica 4 marzo 2007, Gilles Caulier ha scritto:
> Exiv2 to Exiv3 ??? Really Andreas ?
I didn't say it is, but it could ;)

Angelo

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

Alle 18:49, domenica 4 marzo 2007, Gilles Caulier ha scritto:
> Angelo, there is a main binary program to handle metadata by command line,
> like Exiftool work... This program is named exiv2.
??? So yo couldn't call the po files exiv2.po?


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

On Monday 05 March 2007 01:50, Gilles Caulier wrote:
> Exiv2 to Exiv3 ??? Really Andreas ?

2 is part of the name, it is not part of the version.
-ahu.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

On Sunday 04 March 2007 20:49, Gilles Caulier wrote:
> Nota : Andreas, to improve the binary compatibilty, we can use a d
> private internal class everywhere to contain all private members.
>
> Like this, if you add a new private member in a class the benary is
> not broken because private member declarations are include in cpp
> files not in hpp.

I think that would be a good thing. It's just a lot of work.

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

On Monday 05 March 2007 00:21, Angelo Naselli wrote:
> Alle 09:33, sabato 3 marzo 2007, Gilles Caulier ha scritto:
> Other little issue is about translations, why call the files Exiv2?
> all the applications take the same filename as the executable or
> package name, I would have expected exiv2 instead...

Is this a bug? I have no problem changing this. (The autoconf
PACKAGE_NAME has always been Exiv2, that's where it comes from.)

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

[Gilles Caulier-4]

Ah ! Fine for me (:=)))

 

Gilles

 

2007/3/5, Andreas Huggel <[hidden email]>:

On Monday 05 March 2007 01:50, Gilles Caulier wrote:
> Exiv2 to Exiv3 ??? Really Andreas ?

2 is part of the name, it is not part of the version.
-ahu.
_______________________________________________
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

On Sunday 04 March 2007 20:28, Angelo Naselli wrote:
> you can never say from now on i won't
> break it because you change the name of the library and who use the
> old one cannot use the new one without rebuilding itself.

That's a point, especially in view of the changes expected for the next
versions. I will ask distributors to hold back and will release a new
version 0.14 within two weeks with the -version-info versioning system
enabled and whatever bugs fixed that come up until then. This will then
become a stable branch for a while (0.14.x). In parallel, 0.15 (or
maybe another number to make it clearer) and onwards will get the TIFF
write support and some features with major API changes. Does that work
out with digikam's release plans?

In the meantime please test 0.13 to make sure it is useful and can be
the basis for such a stable version. Feedback any problems to the exiv2
group or bug tracker, we shouldn't take-over this list ;)

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

[Gilles Caulier-4]

2007/3/5, Andreas Huggel <[hidden email]>:

On Sunday 04 March 2007 20:28, Angelo Naselli wrote:
> you can never say from now on i won't
> break it because you change the name of the library and who use the
> old one cannot use the new one without rebuilding itself.

That's a point, especially in view of the changes expected for the next
versions. I will ask distributors to hold back and will release a new
version 0.14 within two weeks with the -version-info versioning system
enabled and whatever bugs fixed that come up until then. This will then
become a stable branch for a while (0.14.x). In parallel, 0.15 (or
maybe another number to make it clearer) and onwards will get the TIFF
write support

 

 

Nice nice nice. I'm very impatient to test it, especially to implement a full TIFF image writer witch support full metadata. Actually, libtiff is very limited. We cannot use it to embedded Exif and Makernote informations.

 

Also, later, i will use Exiv2 with libkdcraw to provide a full compliant RAW to DNG converter under linux...

 

 and some features with major API changes. Does that work
out with digikam's release plans?
 

Since we use an external Exiv2 interface (libkexiv2), we just need to update it (:=)))

In the meantime please test 0.13 to make sure it is useful and can be
the basis for such a stable version. Feedback any problems to the exiv2
group or bug tracker, we shouldn't take-over this list ;)

 

I use 0.13 since a long time without problem...
 

Gilles

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

Alle 09:09, lunedì 5 marzo 2007, Andreas Huggel ha scritto:

> On Sunday 04 March 2007 20:28, Angelo Naselli wrote:
> > you can never say from now on i won't
> > break it because you change the name of the library and who use the
> > old one cannot use the new one without rebuilding itself.
>
> That's a point, especially in view of the changes expected for the next
> versions. I will ask distributors to hold back and will release a new
> version 0.14 within two weeks with the -version-info versioning system
> enabled and whatever bugs fixed that come up until then. This will then
> become a stable branch for a while (0.14.x). In parallel, 0.15 (or
> maybe another number to make it clearer) and onwards will get the TIFF
> write support and some features with major API changes. Does that work
> out with digikam's release plans?
>
> In the meantime please test 0.13 to make sure it is useful and can be
> the basis for such a stable version. Feedback any problems to the exiv2
> group or bug tracker, we shouldn't take-over this list ;)

I've just released it for mandriva cooker (2007.1)... and works with new digikam

Angelo

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