Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
Angelo, what is the release date of the next Mandriva version?
This one will include the lat QT 4.3 release and a fresh KDE 4 version to port KDE3 to KDE4 programs ?
Gilles
2007/3/5, Angelo Naselli <[hidden email]>:
Alle 09:09, lunedì 5 marzo 2007, Andreas Huggel ha scritto: ... [show rest of quote] _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
Alle 14:06, lunedì 5 marzo 2007, Gilles Caulier ha scritto:
> Angelo, what is the release date of the next Mandriva version? Well we're frozen, and spring is near ;) > > This one will include the lat QT 4.3 release and a fresh KDE 4 version to > port KDE3 to KDE4 programs ? Well I didn't test it much, as you know i was very buzy this year, i saw some packages including qt4 and kde4 but sure the default is kde 3.x. I believe i'm going to install it soon, hope this weekend and see... Angelo _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel attachment0 (196 bytes) Download Attachment |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
In reply to this post by Bugzilla from ahuggel@gmx.net
Alle 08:33, lunedì 5 marzo 2007, Andreas Huggel ha scritto:
> 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.) no of course not. Only an odd thing compared to package name exiv2, but maybe it's mandriva that changed all to exiv2... Angelo _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel attachment0 (196 bytes) Download Attachment |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
In reply to this post by Bugzilla from anaselli@linux.it
Alle 22:18, lunedì 5 marzo 2007, Angelo Naselli ha scritto:
> Alle 14:06, lunedì 5 marzo 2007, Gilles Caulier ha scritto: > > Angelo, what is the release date of the next Mandriva version? > Well we're frozen, and spring is near ;) > > > > This one will include the lat QT 4.3 release and a fresh KDE 4 version to > > port KDE3 to KDE4 programs ? > Well I didn't test it much, as you know i was very buzy this year, i saw some > packages including qt4 and kde4 but sure the default is kde 3.x. /SRPMS/contrib/release/kdebase4-3.80.3-0.20070228.6mdv2007.1.src.rpm contribs repository > I believe i'm going to install it soon, hope this weekend and see... > > Angelo > _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel attachment0 (196 bytes) Download Attachment |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
In reply to this post by Gilles Caulier-4
Alle 14:06, lunedì 5 marzo 2007, Gilles Caulier ha scritto:
> Angelo, what is the release date of the next Mandriva version? plans are: - RC1 by tomorrow - RC2 next week - Final: March, 19th (GA early April) see <http://wiki.mandriva.com/en/Releases/Mandriva/2007.1/Development> Angelo _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel attachment0 (196 bytes) Download Attachment |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
In reply to this post by Bugzilla from ahuggel@gmx.net
On Sunday, 4. March 2007, Andreas Huggel wrote:
> 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 numbr > 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 General note the important point is for a library backward compatibility of the ABI. Changes in the API/ABI, e.g, adding functions, methods is okay. The release number of a library and API version are two different this. In early days of a library every now version can break ABI backward compatibility, nevertheless the two name different things. A simple change can break the backward compatibility while tons of additions e.g. more/better may not touch the API at all. > versioning system is only meaningful if API/ABI are reasonably stable. > Exiv2 will get there too. Side note: If there a good reason to break the backward compatiblity, good. we have the source we can adapt fix things. Nevertheless ... ;) For distributions an API/ABI change usually mean, that they have to adapt and rebuild, adapting dependencies of all applications that (indirectly) use this library. Especially with dynamicly loaded plugins (e.g. kipi-plugins) preventing that two incompatible version of a libary do not get loaded is hardly trackable automaticly :( So it takes time pickup a new libray interface and integrate it into a distribution. And may therefore delay the inclusion of an application, when a distro is in the conservative period before an release. Don't get me wrong: I'm really glad that exiv2 provides a library interface, making it easier for lots of other applications to make use of it's feature!!!!!!!!!!!!!!!!! Summary: the more often you can delay or workaround an back- wardcompatibilty breaking change, the faster, we the distro- packager, can deliver your great peace of software to our users. > For an example of a subtle API change see > http://uk.groups.yahoo.com/group/exiv2/message/523 After a quick look, I'm sure I miss something ;) About the the parsing of a string by digikam, the breakage due to this subtle change, was either digikam fault (using API the wrong way), or a limitatin in the library interface (providing a onely human readable string, instead of an alternative with computer readable values ;) And e.g. adding methods that return directly usable values without parsing would not break the ABI backward compatibility. So if this was the only suble change ABI change, it would have benn easier adding some methods and/or fix digikam using the lib 'properly' and keeping the backward compatibility of the lib. Last but not least: thx again for you exiv2 work!!! Achim > > Andreas > _______________________________________________ > 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 |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
In reply to this post by Bugzilla from anaselli@linux.it
On Monday, 5. March 2007, Angelo Naselli wrote:
> Alle 08:33, lunedì 5 marzo 2007, Andreas Huggel ha scritto: > > 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.) > no of course not. Only an odd thing compared to package name exiv2, > but maybe it's mandriva that changed all to exiv2... AFAIK debs (for sure) and rpms are always lowercase, aren't they? FWIW: when a libary contains translations and the po file need to contain the API major version too, so translation for libxzy-N and libxyz-M can be installed at the same time. Achim > > Angelo > -- 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 |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
In reply to this post by Bugzilla from ach@mpe.mpg.de
> So it takes time pickup a new libray interface and integrate it > into a distribution. And may therefore delay the inclusion of > an application, when a distro is in the conservative period > before an release. +1 > Summary: the more often you can delay or workaround an back- > wardcompatibilty breaking change, the faster, we the distro- > packager, can deliver your great peace of software to our > users. +1 > > For an example of a subtle API change see > > http://uk.groups.yahoo.com/group/exiv2/message/523 > > After a quick look, I'm sure I miss something ;) > About the the parsing of a string by digikam, the breakage due to > this subtle change, was either digikam fault (using API the wrong way), > or a limitatin in the library interface (providing a onely human > readable string, instead of an alternative with computer readable > values ;) And e.g. adding methods that return directly usable > values without parsing would not break the ABI backward compatibility. > Last but not least: thx again for you exiv2 work!!! Maybe because I'm a distro packager as well??? ;) Angelo _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel attachment0 (196 bytes) Download Attachment |
Free forum by Nabble | Disable Popup Ads | Edit this page |