Added old KDE3 version of libkexiv2

git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/libraries/libkexiv2@1076314 283d02a7-25f6-0310-bc7c-ecb5cbfe19da
v3.5.13-sru
tpearson 15 years ago
commit 03224475f7

@ -0,0 +1,11 @@
AUTHORS AND MAINTAINERS:
Caulier Gilles <caulier dot gilles at gmail dot com>
Marcel Wiesweg <marcel dot wiesweg at gmx dot de>
CONTRIBUTORS:
Angelo Naselli <anaselli at linux dot it>
Gerhard Kulzer <gerhard at kulzer dot net>
Achim Bohnet <ach at mpe dot mpg dot de>

@ -0,0 +1,340 @@
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
51 Franklin Steet, Fifth Floor, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 51 Franklin Steet, Fifth Floor, Boston, MA 02111-1307 USA
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Library General
Public License instead of this License.

@ -0,0 +1,721 @@
V 0.1.7 - 2008-03-24
----------------------------------------------------------------------------
2008-03-18 18:47 cgilles
* [r787192] libkexiv2/libkexiv2.pc.in:
update
2008-03-18 18:37 cgilles
* [r787184] libkexiv2/libkexiv2.lsm, libkexiv2/libkexiv2.pc.in:
update
2008-02-12 07:58 cgilles
* [r773947] libkexiv2/libkexiv2/kexiv2.cpp,
libkexiv2/libkexiv2/kexiv2.h:
libkexiv2 from KDE3 branch : set negative altitude value properly
CCBUGS : 157552
2007-12-30 22:00 anaselli
* [r754872] libkexiv2/libkexiv2/Makefile.am,
libkexiv2/libkexiv2/kexiv2.cpp, libkexiv2/libkexiv2/kexiv2.h:
Breakage of the year, new static method version has been added
CCMAIL: kde-imaging@kde.org
2007-12-14 14:11 cgilles
* [r748437] libkexiv2/libkexiv2.lsm, libkexiv2/libkexiv2.pc.in,
libkexiv2/libkexiv2/version.h:
new version
2007-11-19 15:50 cgilles
* [r738755] libkexiv2/libkexiv2/kexiv2.cpp:
print error code
2007-09-26 10:50 cgilles
* [r717230] libkexiv2/libkexiv2/kexiv2.cpp:
polish
----------------------------------------------------------------------------
V 0.1.6 - 2007-09-08
----------------------------------------------------------------------------
2007-09-01 10:46 cgilles
* [r707242] libkexiv2/libkexiv2/kexiv2.cpp:
libkexiv2 from KDE3 branch : fix IPTC strings creation with
non-zero value at end
CCBUGS: 148182
2007-08-25 08:03 cgilles
* [r704515] libkexiv2/libkexiv2/kexiv2.cpp:
libkexiv2 from KDE3 branch : backport Marcel commit #693337 from
trunk (KDE4) about to handle properly Exiv2 exceptions, depending
of GCC visility option use to compile.
CCBUGS: 148014
--This l from KDEine, and those below, will be ignored--
M kexiv2.cpp
2007-08-21 20:48 cgilles
* [r703058] libkexiv2/libkexiv2/kexiv2.cpp:
use EXIV2_TEST_VERSION instead EXIV2_CHECK_VERSION witch is
depreciate now
2007-08-21 18:54 cgilles
* [r703007] libkexiv2/libkexiv2/kexiv2.cpp:
fix EXIV2_CHECK_VERSION macro handling
2007-08-21 09:16 cgilles
* [r702839] libkexiv2/libkexiv2/kexiv2.cpp:
libkexiv2 from KDE3 branch : return run-time version if Exiv2 if
possible
2007-06-13 08:12 cgilles
* [r674817] libkexiv2/libkexiv2/kexiv2.cpp:
libkexiv2 from KDE3 branch : With Nikon camera, the AdobeRgb user
color space is defined to set Exif.Photo.ColorSpace to
Uncalibrated and Exif.Nikon3.ColorMode to MODE2.
BUG: 137750
2007-06-08 19:16 cgilles
* [r673015] libkexiv2/Makefile.am, libkexiv2/kexiv2.cpp,
libkexiv2/kexiv2.h, libkexiv2/libkexiv2,
libkexiv2/libkexiv2/Makefile.am, libkexiv2/libkexiv2/kexiv2.cpp,
libkexiv2/libkexiv2/kexiv2.h,
libkexiv2/libkexiv2/libkexiv2_export.h,
libkexiv2/libkexiv2/version.h, libkexiv2/libkexiv2_export.h,
libkexiv2/version.h:
to be homogenous with trunk (KDE4), move all source code in
libkexiv2 sub-folder
2007-06-05 06:56 cgilles
* [r671625] libkexiv2/kexiv2.cpp, libkexiv2/kexiv2.h:
libkexiv2 from branches : Krazy Code Checker fix
(http://www.englishbreakfastnetwork.org/krazy)
2007-06-05 06:29 cgilles
* [r671618] libkexiv2/kexiv2.cpp:
libkexiv2 from branches : Krazy Code Checker fix
(http://www.englishbreakfastnetwork.org/krazy)
2007-06-04 11:35 cgilles
* [r671273] libkexiv2/CMakeLists.txt, libkexiv2/cmake:
remove obsolete file
----------------------------------------------------------------------------
V 0.1.5 - 2007-05-08
----------------------------------------------------------------------------
Fixing: libtools version info again, we found not to be back compatible
with libkexiv 0.1.1, unfortunately since 0.1.2 version.
----------------------------------------------------------------------------
V 0.1.4 - 2007-05-06
----------------------------------------------------------------------------
Fixing: libtools version info
2007-05-06 21:23 anaselli
* [r661885] libkexiv2/ChangeLog, libkexiv2/Makefile.am,
libkexiv2/libkexiv2.lsm, libkexiv2/libkexiv2.pc.in,
libkexiv2/version.h:
Release 0.1.4
- fix libtools version-info
CCMAIL: kde-imaging@kde.org, digikam-devel@kde.org
2007-05-06 21:14 anaselli
* [r661883] libkexiv2/Makefile.am:
Changed to add libtools version managing into prepare script
(hope this will avoid to forget it)
----------------------------------------------------------------------------
v 0.1.3 - 2007-05-05
----------------------------------------------------------------------------
2007-05-05 14:01 gkulzer
* [r661413] libkexiv2/ChangeLog:
0.1.3 release, coordinated with digiKam 0.9.2-beta1 release
2007-05-05 12:09 gkulzer
* [r661379] libkexiv2/ChangeLog, libkexiv2/NEWS,
libkexiv2/libkexiv2.lsm:
0.1.3 release, coordinated with digiKam 0.9.2-beta1 release
2007-05-02 07:11 cgilles
* [r660285] libkexiv2/kexiv2.cpp, libkexiv2/kexiv2.h,
libkexiv2/libkexiv2_export.h, libkexiv2/version.h:
fix headers
2007-05-02 06:42 cgilles
* [r660276] libkexiv2/kexiv2.cpp, libkexiv2/kexiv2.h:
libkexiv2 from trunk : test if file is readable before to load it
in Exiv2.
CCBUGS: 144895
* [r658899] BUG:144455
thanks a lot to Stéphane Pontier, corrected a lot of spelling errors
and missing mails
M /trunk/extragear/libs/libkexiv2/libkexiv2_export.h
M /trunk/extragear/libs/libkexiv2/kexiv2.cpp
M /trunk/extragear/libs/libkexiv2/version.h
M /trunk/extragear/libs/libkexiv2/kexiv2.h
* [r658847] GPS problem solved. BUG:144604
M /trunk/extragear/libs/libkexiv2/kexiv2.cpp
Gilles patch
* [r658711]M /trunk/extragear/libs/libkexiv2/libkexiv2.pc.in
M /trunk/extragear/libs/libkexiv2/kexiv2.cpp
M /trunk/extragear/libs/libkexiv2/libkexiv2.lsm
M /trunk/extragear/libs/libkexiv2/version.h
M /trunk/extragear/libs/libkexiv2/NEWS
M /trunk/extragear/libs/libkexiv2/README
M /trunk/extragear/libs/libkexiv2/kexiv2.h
V 0.1.2 - 2007-04-07
----------------------------------------------------------------------------
2007-03-26 07:54 cgilles
* [r646581] libkexiv2/kexiv2.cpp, libkexiv2/kexiv2.h:
libkexiv2 from trunk : polish API : all "get...()" method must
use const operator.
2007-03-15 11:10 anaselli
* [r642771] libkexiv2/Makefile.am, libkexiv2/NEWS:
API changed, please check if it is correct.
CCMAIL: caulier.gilles@kdemail.net
2007-03-15 09:09 cgilles
* [r642722] libkexiv2/kexiv2.cpp, libkexiv2/kexiv2.h:
libkexiv2 from trunk : Fix broken compilation with current Exiv2
implementation (next 0.14.0 release), duing a change with C++
Exception rule. I recommend to cleanup and recompile this library
and clients program witch use it.
Note : libkexiv2 still compatible with older Exiv2 releases 0.12
and 0.13
CCMAIL: digikam-devel@kde.org
2007-03-14 12:12 cgilles
* [r642432] libkexiv2/NEWS:
--Cette ligupdatene, et les suivantes ci-dessous, seront
ignorées--
M NEWS
2007-03-14 12:11 cgilles
* [r642431] libkexiv2/kexiv2.cpp:
libkexiv2 from trunk : patch from Arnd Baecker about to avoid the
GPS accuracy loss
BUG: 140297
2007-03-14 12:05 cgilles
* [r642427] libkexiv2/kexiv2.cpp:
sanity check again about empty byte array
2007-03-14 11:58 cgilles
* [r642421] libkexiv2/libkexiv2.lsm:
fix version
2007-03-14 11:58 cgilles
* [r642420] libkexiv2/libkexiv2.pc.in:
fix version
2007-03-14 11:57 cgilles
* [r642419] libkexiv2/version.h:
fix version
2007-03-11 10:58 cgilles
* [r641445] libkexiv2/kexiv2.cpp:
libkexiv2 from trunk : when Exiv2 0.14.0 will be available, a new
tag Exif.Image.ProcessingSoftware will be use to store program
informations
2007-03-11 10:31 cgilles
* [r641437] libkexiv2/NEWS:
update
2007-03-11 10:30 cgilles
* [r641436] libkexiv2/kexiv2.cpp:
fix comment
2007-03-11 10:29 cgilles
* [r641435] libkexiv2/kexiv2.cpp:
libkexiv2 from trunk : set the Exif.Image.Software tag only if it
doesn't exist.
BUG: 142564
2007-02-28 22:19 ach
* [r638128] libkexiv2:
libkexiv2: ignore Makefile.in
2007-02-28 22:14 ach
* [r638127] libkexiv2/kexiv2.cpp, libkexiv2/kexiv2.h,
libkexiv2/libkexiv2_export.h, libkexiv2/version.h:
libkexiv2: remove unnecessary line break in license notice
2007-02-28 22:13 ach
* [r638126] libkexiv2/AUTHORS:
libkexiv2: add final newline to AUTHORS
----------------------------------------------------------------------------
V 0.1.1 - 2007-02-24
----------------------------------------------------------------------------
2007-02-24 20:53 anaselli
* [r636958] libkexiv2/ChangeLog, libkexiv2/Makefile.am,
libkexiv2/NEWS, libkexiv2/libkexiv2.lsm,
libkexiv2/libkexiv2.pc.in, libkexiv2/version.h:
libkexiv2 0.1.1
bug fixing release
CCMAIL:kde-imaging@kde.org
2007-02-22 12:01 cgilles
* [r636211] kipi-plugins/kipiplugins.kdevelop,
kipi-plugins/rawconverter/batchdialog.cpp,
kipi-plugins/rawconverter/singledialog.cpp,
libkdcraw/dcraw/dcraw.c, libkdcraw/dcraw/kdcraw.1,
libkdcraw/dcrawbinary.cpp, libkdcraw/dcrawsettingswidget.cpp,
libkdcraw/dcrawsettingswidget.h, libkdcraw/kdcraw.cpp,
libkdcraw/libkdcraw.kdevelop, libkdcraw/rawdecodingsettings.h,
libkexiv2/libkexiv2.kdevelop:
libkdcraw from trunk : backport last dcraw implementation "8.60"
: the old noise reduction algorithm used with 8.54 version have
been remplaced by a wavelet algorithm witch is more intuitive,
more easy to use (just one threshold setting) and very powerfull.
Kipi-plugins RAWConverter from svn trunk is fixed.
The patch to use libkdcraw with current implementation of digiKam
have been updated :
http://digikam3rdparty.free.fr/misc.tarballs/libkdcrawdigikamport.patch
CCMAIL: digikam-users@kde.org
CCMAIL: digikam-devel@kde.org
CCMAIL: kde-imaging@kde.org
2007-02-20 17:22 cgilles
* [r635684] libkexiv2/kexiv2.cpp:
libkexiv2 from trunk : sanity check if QByteArray are null size
everywhere
Feedback welcome...
CCBUGS:141980
2007-02-16 22:01 cgilles
* [r634334] kipi-plugins/rawconverter/actionthread.cpp,
kipi-plugins/rawconverter/rawdecodingiface.cpp,
libkdcraw/kdcraw.cpp, libkexiv2/kexiv2.cpp:
fix comments
2007-02-16 15:44 cgilles
* [r634186] libkexiv2/libkexiv2.kdevelop:
kdevelop project
2007-02-16 15:44 cgilles
* [r634184] libkexiv2/AUTHORS, libkexiv2/kexiv2.cpp,
libkexiv2/kexiv2.h, libkexiv2/libkexiv2.lsm:
fix email
2007-02-15 13:15 cgilles
* [r633835] libkexiv2/kexiv2.cpp:
indent
2007-02-13 22:41 ach
* [r633377] libkexiv2/README:
fix library name in README
2007-02-12 15:26 cgilles
* [r632868] libkexiv2/configure.in.in:
this condition is unused everywhere. removed
2007-02-12 09:24 cgilles
* [r632763] libkexiv2/configure.in.in:
revert
2007-02-12 08:32 cgilles
* [r632755] libkexiv2/configure.in.in:
polish
----------------------------------------------------------------------------
V 0.1.0 - 2007-02-11
----------------------------------------------------------------------------
2007-02-11 20:44 anaselli
* [r632646] libkexiv2/ChangeLog, libkexiv2/libkexiv2.lsm,
libkexiv2/libkexiv2.pc.in:
libkexiv2 0.1.0
CCMAIL:kde-imaging@kde.org
2007-02-09 06:50 cgilles
* [r631791] libkexiv2/kexiv2.cpp, libkexiv2/kexiv2.h:
libkexiv2 from trunk : new method to extract Exiv2 library
release numbers
2007-02-06 22:12 cgilles
* [r630973] libkexiv2/version.h:
compile
2007-02-06 22:04 cgilles
* [r630967] libkexiv2/Makefile.am, libkexiv2/version.h:
libkexiv2 from trunk : add version header file for this library
CCMAIL: Achim Bohnet <ach@mpe.mpg.de>
2007-02-06 21:39 cgilles
* [r630957] libkexiv2/kexiv2.cpp, libkexiv2/kexiv2.h:
2 new methods to set IPTC or Exif tag using a bytes array
2007-02-05 20:16 cgilles
* [r630585] libkexiv2/kexiv2.cpp, libkexiv2/kexiv2.h:
factorize source code
2007-02-05 14:38 cgilles
* [r630488] libkexiv2/kexiv2.cpp, libkexiv2/kexiv2.h:
add boolean flag to add or not program name when a tag is
changed/added
2007-02-05 14:00 cgilles
* [r630471] libkexiv2/kexiv2.h:
set load() like virtual method. Re-implemented in digiKam core
2007-01-30 12:18 cgilles
* [r628573] libkexiv2/README:
update
2007-01-30 12:16 cgilles
* [r628572] libkexiv2/README:
update
2007-01-30 12:12 cgilles
* [r628569] libkexiv2/README:
update
2007-01-30 11:57 cgilles
* [r628566] libkexiv2/kexiv2.cpp, libkexiv2/kexiv2.h:
libkexiv2 from trunk : polish implementation. Fix API doc
2007-01-30 11:18 cgilles
* [r628554] libkexiv2/kexiv2.h:
libkexiv2 from trunk : Finamize API doc.
2007-01-30 10:23 cgilles
* [r628541] libkexiv2/kexiv2_export.h:
wrong file name
2007-01-30 10:22 cgilles
* [r628540] kipi-plugins/galleryexport/gallerytalker.cpp,
kipi-plugins/gpssync/gpslistviewitem.cpp,
kipi-plugins/gpssync/plugin_gpssync.cpp,
kipi-plugins/jpeglossless/jpegtransform.h,
kipi-plugins/metadataedit/exifadjust.cpp,
kipi-plugins/metadataedit/exifcaption.cpp,
kipi-plugins/metadataedit/exifdatetime.cpp,
kipi-plugins/metadataedit/exifdevice.cpp,
kipi-plugins/metadataedit/exifeditdialog.cpp,
kipi-plugins/metadataedit/exiflens.cpp,
kipi-plugins/metadataedit/exiflight.cpp,
kipi-plugins/metadataedit/iptccaption.cpp,
kipi-plugins/metadataedit/iptccategories.cpp,
kipi-plugins/metadataedit/iptccredits.cpp,
kipi-plugins/metadataedit/iptcdatetime.cpp,
kipi-plugins/metadataedit/iptceditdialog.cpp,
kipi-plugins/metadataedit/iptckeywords.cpp,
kipi-plugins/metadataedit/iptcorigin.cpp,
kipi-plugins/metadataedit/iptcstatus.cpp,
kipi-plugins/metadataedit/iptcsubjects.cpp,
kipi-plugins/metadataedit/plugin_metadataedit.cpp,
kipi-plugins/rawconverter/dcrawiface.cpp,
kipi-plugins/sendimages/sendimages.cpp,
kipi-plugins/timeadjust/timeadjustdialog.cpp,
libkexiv2/Makefile.am, libkexiv2/kexiv2.cpp, libkexiv2/kexiv2.h,
libkexiv2/kexiv2_export.h, libkexiv2/libkexiv2.cpp,
libkexiv2/libkexiv2.h:
kipi-plugins from trunk : fix libkexiv2 header file name
2007-01-30 09:45 cgilles
* [r628536] kipi-plugins/galleryexport/gallerytalker.cpp,
kipi-plugins/gpssync/gpslistviewitem.cpp,
kipi-plugins/gpssync/plugin_gpssync.cpp,
kipi-plugins/jpeglossless/jpegtransform.cpp,
kipi-plugins/jpeglossless/jpegtransform.h,
kipi-plugins/metadataedit/exifadjust.cpp,
kipi-plugins/metadataedit/exifcaption.cpp,
kipi-plugins/metadataedit/exifdatetime.cpp,
kipi-plugins/metadataedit/exifdevice.cpp,
kipi-plugins/metadataedit/exifeditdialog.cpp,
kipi-plugins/metadataedit/exiflens.cpp,
kipi-plugins/metadataedit/exiflight.cpp,
kipi-plugins/metadataedit/iptccaption.cpp,
kipi-plugins/metadataedit/iptccategories.cpp,
kipi-plugins/metadataedit/iptccredits.cpp,
kipi-plugins/metadataedit/iptcdatetime.cpp,
kipi-plugins/metadataedit/iptceditdialog.cpp,
kipi-plugins/metadataedit/iptckeywords.cpp,
kipi-plugins/metadataedit/iptcorigin.cpp,
kipi-plugins/metadataedit/iptcstatus.cpp,
kipi-plugins/metadataedit/iptcsubjects.cpp,
kipi-plugins/metadataedit/plugin_metadataedit.cpp,
kipi-plugins/rawconverter/dcrawiface.cpp,
kipi-plugins/sendimages/sendimages.cpp,
kipi-plugins/timeadjust/timeadjustdialog.cpp,
libkexiv2/libkexiv2.cpp, libkexiv2/libkexiv2.h:
kipi-plugins from trunk : fix libkexiv2 namespace and interface
class name
2007-01-30 09:02 cgilles
* [r628532] libkexiv2/libkexiv2.cpp, libkexiv2/libkexiv2.h:
libkexiv2 from trunk : backport new method to handle color
work-space of image. update API doc.
2007-01-29 23:36 ach
* [r628396] libkexiv2/libkexiv2.h:
libkexiv2: s/informations/information/
2007-01-29 21:19 lure
* [r628356] libkexiv2/libkexiv2.h:
Fix broken comment - did not compile on Kubuntu Feisty
2007-01-29 19:57 cgilles
* [r628333] libkexiv2/libkexiv2.h:
libkexiv2 from trunk : Doxygen API (uncomplete)
2007-01-29 16:49 cgilles
* [r628263] libkexiv2/libkexiv2.pc.in:
update
2007-01-29 14:18 cgilles
* [r628206] libkexiv2/libkexiv2.cpp, libkexiv2/libkexiv2.h:
libkexiv2 from trunk : backport all common methods from
Digikam::DMetadata class. Backport all fix about comments
encoding from Marcel. The implementation is clean now and ready
to use with digiKam core.
CCMAIL : marcel.wiesweg@gmx.de, digikam-devel@kde.org,
kde-imaging@kde.org
2007-01-29 09:50 cgilles
* [r628140] libkexiv2/libkexiv2.cpp, libkexiv2/libkexiv2.h:
new protected methods to use with derivated class
2007-01-28 10:32 ach
* [r627809] libkexiv2/libkexiv2.lsm, libkexiv2/libkexiv2.pc.in,
prepare_libkexiv2.rb:
libkexiv2: use same version everywhere
2007-01-28 09:54 ach
* [r627801] libkexiv2/libkexiv2.pc.in:
libkexiv2: fix libkexiv2.pc pkg-config file
2007-01-28 09:47 ach
* [r627799] libkexiv2/configure.in.in:
libkexiv2: Fix configure. PKGCONFIGFOUND was not set.
CCMAIL: kde-imaging@kde.org
2007-01-27 12:40 cgilles
* [r627622] libkexiv2/libkexiv2.cpp, libkexiv2/libkexiv2_export.h:
kipi-plugins from trunk : libkexiv2 : do not use kdDebug() here
because it's not thread-safe. Use qDebug() instead...
CCBUGS: 133026
2007-01-27 10:57 cgilles
* [r627593] libkexiv2/README:
update
2007-01-26 20:59 cgilles
* [r627509] libkexiv2/libkexiv2.lsm:
update
2007-01-26 20:40 cgilles
* [r627501] kipi-plugins/NEWS, kipi-plugins/README,
kipi-plugins/common/Makefile.am, kipi-plugins/common/exiv2iface,
kipi-plugins/configure.in.bot, kipi-plugins/configure.in.in,
kipi-plugins/galleryexport/Makefile.am,
kipi-plugins/galleryexport/gallerytalker.cpp,
kipi-plugins/gpssync/Makefile.am,
kipi-plugins/gpssync/gpslistviewitem.cpp,
kipi-plugins/gpssync/gpslistviewitem.h,
kipi-plugins/gpssync/plugin_gpssync.cpp,
kipi-plugins/gpssync/plugin_gpssync.h,
kipi-plugins/jpeglossless/Makefile.am,
kipi-plugins/jpeglossless/jpegtransform.cpp,
kipi-plugins/jpeglossless/jpegtransform.h,
kipi-plugins/metadataedit/Makefile.am,
kipi-plugins/metadataedit/exifadjust.cpp,
kipi-plugins/metadataedit/exifcaption.cpp,
kipi-plugins/metadataedit/exifdatetime.cpp,
kipi-plugins/metadataedit/exifdevice.cpp,
kipi-plugins/metadataedit/exifeditdialog.cpp,
kipi-plugins/metadataedit/exiflens.cpp,
kipi-plugins/metadataedit/exiflight.cpp,
kipi-plugins/metadataedit/iptccaption.cpp,
kipi-plugins/metadataedit/iptccategories.cpp,
kipi-plugins/metadataedit/iptccredits.cpp,
kipi-plugins/metadataedit/iptcdatetime.cpp,
kipi-plugins/metadataedit/iptceditdialog.cpp,
kipi-plugins/metadataedit/iptckeywords.cpp,
kipi-plugins/metadataedit/iptcorigin.cpp,
kipi-plugins/metadataedit/iptcstatus.cpp,
kipi-plugins/metadataedit/iptcsubjects.cpp,
kipi-plugins/metadataedit/plugin_metadataedit.cpp,
kipi-plugins/rawconverter/Makefile.am,
kipi-plugins/rawconverter/dcrawiface.cpp,
kipi-plugins/rawconverter/dcrawiface.h,
kipi-plugins/sendimages/Makefile.am,
kipi-plugins/sendimages/sendimages.cpp,
kipi-plugins/sendimages/sendimages.h,
kipi-plugins/sync/Makefile.am,
kipi-plugins/sync/gallerytalker.cpp,
kipi-plugins/timeadjust/Makefile.am,
kipi-plugins/timeadjust/timeadjustdialog.cpp,
kipi-plugins/timeadjust/timeadjustdialog.h,
libkexiv2/libkexiv2.cpp, libkexiv2/libkexiv2.h:
kipi-plugins from trunk : all plugins use the new shared library
libkexiv2 instead KipiPlugins::EXiv2Iface class.
Marcel, next stage is to derivate the DigiKam::DMetadata class
from LibKExiv2. Let's me hear when you whant to do it...
CCMAIL: digikam-devel@kde.org, kde-imaging@kde.org,
marcel.wiesweg@gmx.de
2007-01-26 15:51 cgilles
* [r627439] libkexiv2/configure.in.bot, libkexiv2/configure.in.in:
compile
2007-01-26 15:38 cgilles
* [r627433] libkexiv2/libkexiv2.h:
using Export rules
2007-01-26 13:14 cgilles
* [r627401] libkexiv2/README:
update
2007-01-26 13:10 cgilles
* [r627400] libkexiv2/README:
update
2007-01-26 13:09 cgilles
* [r627399] libkexiv2/Makefile.am, libkexiv2/exiv2iface.cpp,
libkexiv2/exiv2iface.h, libkexiv2/libkexiv2.cpp,
libkexiv2/libkexiv2.h:
exiv2iface ==> libkexiv2
new namespace
2007-01-26 12:58 cgilles
* [r627393] libkexiv2/exiv2iface.cpp, libkexiv2/exiv2iface.h,
libkexiv2/libkexiv2_export.h:
fix header
2007-01-26 12:55 cgilles
* [r627390] libkexiv2, libkexiv2/AUTHORS, libkexiv2/COPYING,
libkexiv2/ChangeLog, libkexiv2/INSTALL, libkexiv2/Makefile.am,
libkexiv2/NEWS, libkexiv2/README, libkexiv2/configure.in.in,
libkexiv2/exiv2iface.cpp, libkexiv2/exiv2iface.h,
libkexiv2/libkexiv2.lsm, libkexiv2/libkexiv2.pc.in,
libkexiv2/libkexiv2_export.h:
New common library witch will be used by digiKam and kipi-plugins
to handle Pictures metadata (Exif/Iptc).
This shared library is a wrapper around Exiv2 library. It give a
Qt like interface to control
Exiv2 actions on pictures. Using this library will remove all
duplicate code on kipi-plugins::exiv2iface and
digikam::dmetadata.
The current implementation is the same than
kipi-plugins/exiv2iface. This library is not yet used in
digiKam/kipi-plugins.
We will added a new depency to this library in kipi-plugins in
first and later to digiKam.
CCMAIL: digikam-devel@kde.org, kde-imaging@kde.org,
marcel.wiesweg@gmx.de

@ -0,0 +1,181 @@
Basic Installation
==================
These are generic installation instructions.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, a file
`config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output
(useful mainly for debugging `configure').
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.
The file `configure.in' is used to create `configure' by a program
called `autoconf'. You only need `configure.in' if you want to change
it or regenerate `configure' using a newer version of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.
Running `configure' takes awhile. While running, it prints some
messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with
the package.
4. Type `make install' to install the programs and any data files and
documentation.
5. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
Compilers and Options
=====================
Some systems require unusual options for compilation or linking that
the `configure' script does not know about. You can give `configure'
initial values for variables by setting them in the environment. Using
a Bourne-compatible shell, you can do that on the command line like
this:
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
Or on systems that have the `env' program, you can do it like this:
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
Compiling For Multiple Architectures
====================================
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
If you have to use a `make' that does not supports the `VPATH'
variable, you have to compile the package for one architecture at a time
in the source code directory. After you have installed the package for
one architecture, use `make distclean' before reconfiguring for another
architecture.
Installation Names
==================
By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc. You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.
In addition, if you use an unusual directory layout you can give
options like `--bindir=PATH' to specify different values for particular
kinds of files. Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Optional Features
=================
Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
Specifying the System Type
==========================
There may be some features `configure' can not figure out
automatically, but needs to determine by the type of host the package
will run on. Usually `configure' can figure that out, but if it prints
a message saying it can not guess the host type, give it the
`--host=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:
CPU-COMPANY-SYSTEM
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the host type.
If you are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system they will
produce code for and the `--build=TYPE' option to select the type of
system on which you are compiling the package.
Sharing Defaults
================
If you want to set default values for `configure' scripts to share,
you can create a site shell script called `config.site' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Operation Controls
==================
`configure' recognizes the following options to control how it
operates.
`--cache-file=FILE'
Use and save the results of the tests in FILE instead of
`./config.cache'. Set FILE to `/dev/null' to disable caching, for
debugging `configure'.
`--help'
Print a summary of the options to `configure', and exit.
`--quiet'
`--silent'
`-q'
Do not print messages saying which checks are being made.
`--srcdir=DIR'
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
`--version'
Print the version of Autoconf used to generate the `configure'
script, and exit.
`configure' also accepts some other, not widely useful, options.

@ -0,0 +1,7 @@
/** @mainpage KDE Extragear Libraries
*
* The extragear-libs module collects libraries that are shared by
* more than one extragear application, or which are useful in their
* own right.
*
*/

@ -0,0 +1,7 @@
AUTOMAKE_OPTIONS = foreign 1.6.1
include admin/deps.am
include admin/Doxyfile.am
COMPILE_FIRST = libkexiv2 libkipi libkdcraw
SUBDIRS=$(TOPSUBDIRS)

@ -0,0 +1,6 @@
AUTOMAKE_OPTIONS = foreign 1.6.1
include admin/deps.am
include admin/Doxyfile.am
COMPILE_FIRST = libkexiv2 libkipi libkdcraw

@ -0,0 +1,14 @@
all:
@echo "This Makefile is only for the CVS repository"
@echo "This will be deleted before making the distribution"
@echo ""
@if test ! -d admin; then \
echo "Please recheckout this module!" ;\
echo "for cvs: use checkout once and after that update again" ;\
echo "for cvsup: checkout kde-common from cvsup and" ;\
echo " link kde-common/admin to ./admin" ;\
exit 1 ;\
fi
$(MAKE) -f admin/Makefile.common cvs
.SILENT:

60
NEWS

@ -0,0 +1,60 @@
0.1.7
------------------------------------------------------------------------
API changes: Added a version method to get runtime library version.
Bugs fixed from B.K.O (http://bugs.kde.org):
001 ==> 157552: negative altitudes are not shown in metadata GPS sidebar
0.1.6
------------------------------------------------------------------------
- API Changed : Kexiv2 destructor is now virtual.
Krazy Code Checker fix (http://www.englishbreakfastnetwork.org/krazy)
Bugs fixed from B.K.O (http://bugs.kde.org):
001 ==> 137750: color mode2 nikon d70s not recognized as adobe rgb
002 ==> 149267: digiKam crashes after finding gif,avi,txt and so on.
003 ==> 148182: Iptc.Application2.Keywords appends always the 0-byte.
0.1.5
------------------------------------------------------------------------
Fix release version informations.
0.1.4
------------------------------------------------------------------------
Fix release version informations.
0.1.3
------------------------------------------------------------------------
New features
- API changed: added 4 new static methods to get Exif/Iptc tags description/title.
moved depreceate protected methods used by digiKam core to private.
Bugs fixed from B.K.O (http://bugs.kde.org):
001 ==> 144604: Rotation causes Exif data corruption. GPS data fix
General : Make size of icons used in album icon view more configurable using a slider
in status bar.
General : Removing direct Exiv2 library depency. libkexiv2 interface is used everywhere
instead.
0.1.2
------------------------------------------------------------------------
New features
- added support for exiv2 from svn (next 0.14.0 release)
- API changed: added printExiv2ExceptionError to manage Exiv2 C++ Exception error message
Bugs fixed from B.K.O (http://bugs.kde.org):
001 ==> 142564: digiKam-signature in iptc and exif tags.
002 ==> 140297: GPS kipi plugin truncates input coordinates, introducing inacuracy.
0.1.1
------------------------------------------------------------------------
Bugs fixed from B.K.O (http://bugs.kde.org):
001 ==> 141980: digiKam crash when rescan certain files exiv2.
0.1.0
------------------------------------------------------------------------
First implementation
For details and info about previous versions, see ChangeLog.

@ -0,0 +1,205 @@
How to release kipi & co.
----------------------------------------
1. Before the final release
2. Release libkipi
3. Release libkexiv2
4. Release kipi-plugins
5. Notes on svn2cl
----------------------------------------
1. Before the final release
----------------------------------------
Some days before releasing the final, remember to announce
the translations commit deadline to kde-i18-doc@kde.org.
----------------------------------------
2. Release libkipi
----------------------------------------
a) Update release info
libkipi/libkipi.lsm
libkipi/libkipi/version.h
libkipi/libkipi.pc.in
To do that you can use the "prepare_libkipi.rb" script, change the
release version ("version" and "version_n" fields) and run it.
Don't forget to commit your changes :)
b) Update Changelog
- to do that use the "release_kipi_changelog.sh" script
release_kipi_changelog.sh libkipi oldest-revision-or-date new-release-version
- edit Changelog and modify the wrong lines (if any)
- Commit your changes
c) Build the source tarball
- use the "release_libkipi.rb"
edit the script and change the "version" field
if you're releasing an svn snapshot set "usesvnver" to "yes"
run it and get libkipiXXX.tar.bz2
d) Uncompress and test the tarball
- check if all the files are right in
- check if the file RELEASE.rev is in and with the right revision number
- check if it builds correctly.
- diff headerfiles installed in <incdir>/kde/libkipi/ with last release
and check for binary compatibility (see e.g.,
http://developer.kde.org/documentation/other/binarycompatibility.html)
Every API change should be refleced in a changed version-info in
libkipi/libkipi/Makefile.am (see e.g.,
http://www.gnu.org/software/libtool/manual.html#Versioning)
e) Upload tarball for testing
Before an official release upload the tarball for testing used sites are
digikam3rdparty.free.fr or www.linux.it/~anaselli/kipi-plugins - depends
on who is releasing :)
Send a mail to kde-imaging@kde.org and digikam-devel@kde.org to have a
feedback from pakagers before posting an offical release annoucement.
f) Upload tarbal on SF and update kipi site
official site for uploading the release is http://sourceforge.net/projects/kipi
web page to be update is http://extragear.kde.org/apps/kipi/
to update this last you have to get, change and commit it from
XXX@svn.kde.org/home/kde/trunk/www/areas/extragear/apps/kipi
Send a mail to announce the official release.
----------------------------------------
3. Release libkexiv2
----------------------------------------
a) Update release info
libkexiv2/libkexiv2.lsm
libkexiv2/version.h
libkexiv2/libkexiv2.pc.in
libkexiv2/Makefile.am
libkexiv2/ChangeLog
To do that you can use the "prepare_libkexiv2.rb" script, change the
release version ("version", "version_n", "version_info" and "chlog_rev" fields)
and run it.
Don't forget to fix Changelog and commit your changes :)
c) Build the source tarball
- use the "release_libkexiv2.rb"
edit the script and change the "version" field
if you're releasing an svn snapshot set "usesvnver" to "yes"
run it and get libkexiv2XXX.tar.bz2
d) Uncompress and test the tarball
- check if all the files are right in
- check if the file RELEASE.rev is in and with the right revision number
- check if it builds correctly.
- diff headerfiles installed in <incdir>/kde/libkexiv2/ with last release
and check for binary compatibility (see e.g.,
http://developer.kde.org/documentation/other/binarycompatibility.html)
Every API change should be refleced in a changed version-info in
libkexiv2/Makefile.am (see e.g.,
http://www.gnu.org/software/libtool/manual.html#Versioning)
e) Upload tarball for testing
Before an official release upload the tarball for testing used sites are
digikam3rdparty.free.fr or www.linux.it/~anaselli/kipi-plugins - depends
on who is releasing :)
Send a mail to kde-imaging@kde.org and digikam-devel@kde.org to have a
feedback from pakagers before posting an offical release annoucement.
f) Upload tarbal on SF and update kipi site
official site for uploading the release is http://sourceforge.net/projects/kipi
web page to be update is http://extragear.kde.org/apps/kipi/
to update this last you have to get, change and commit it from
XXX@svn.kde.org/home/kde/trunk/www/areas/extragear/apps/kipi
Send a mail to announce the official release.
----------------------------------------
4. Release kipi-plugins
----------------------------------------
a) Update release info
kipi-plugins/kipi-plugins.lsm
kipi-plugins/common/include/pluginsversion.h
(kipi-plugins/ChangeLog)
To do that you can use the "prepare_kipiplugins.rb" script, change the
release version ("version" field) and run it.
Using svn2cl (http://ch.tudelft.nl/~arthur/svn2cl/) you can
add ChangeLog info with this script as well, to do that
follow the instructions:
- set usesv2cl to "yes"
- set svn2cl, svnbase, svnroot according to your account
- set chlog_rev to the last revision (+1) of the last release
(look at ChangeLog file, last commit)
- use the script as usual and skip step b)
- edit ChangeLog and modify the wrong lines (if any)
Don't forget to commit your changes.
b) Update ChangeLog
- if you're using svn2cl you can do that at step a)
- to do that use the "release_kipi_changelog.sh" script
release_kipi_changelog.sh kipi-plugins oldest-revision-or-date new-release-version
- edit Changelog and modify the wrong lines (if any)
- Commit your changes
c) Build the source tarball
- use the "release_kipi-plugins.rb"
edit the script and change the "version" field and check the "addPo" one for po files
if you're releasing an svn snapshot set "usesvnver" to "yes"
run it and get kipi-pluginsXXX.tar.bz2
d) Uncompress and test the tarball
- check if all the files are right in
- check if the file RELEASE.rev is in and with the right revision number
- check if it builds correctly.
e) Upload tarball for testing
Before an official release upload the tarball for testing used sites are
digikam3rdparty.free.fr or www.linux.it/~anaselli/kipi-plugins - depends
on who is releasing :)
Send a mail to kde-imaging@kde.org and digikam-devel@kde.org to have a
feedback from pakagers before posting an offical release annoucement.
f) Upload tarbal on SF and update kipi site
official site for uploading the release is http://sourceforge.net/projects/kipi
web page to be update is http://extragear.kde.org/apps/kipi/
to update this last you have to get, change and commit it from
XXX@svn.kde.org/home/kde/trunk/www/areas/extragear/apps/kipi
Send a mail to announce the official release at least to:
- kde-extra-gear@kde.org
- kde-announce@kde.org
- kde-imaging@kde.org
- digikam-devel@kde.org
- gwenview-general@lists.sourceforge.net
----------------------------------------
5. Notes on svn2cl
----------------------------------------
Latest versions (>= 0.9) of svn2cl offer the --ignore-message-starting option
and --ignore-message-starting=SVN_SILENT should work.
Programmers often write SVN_SILENT or CVS_SILENT (obsolete) everywhere
in the commit comment, that means such an option could not work.
Moreover it can be used only once, so just to skip SVN_SILENT or CVS_SILENT
not both.
The easiest way was to to hack into svn2cl.xsl (mine is /usr/share/svn2cl/svn2cl.xsl).
Add the following lines:
<!-- skip entries where the message contains SVN_SILENT -->
<xsl:template match="logentry[contains(msg,'SVN_SILENT')]">
</xsl:template>
<!-- skip entries where the message contains SILENT -->
<xsl:template match="logentry[contains(msg,'SILENT')]">
</xsl:template>
just before the template:
<!-- format one entry from the log -->
<xsl:template match="logentry">
...

@ -0,0 +1,25 @@
EXIV2 Library interface for KDE
This library is a part of Kipi-Plugins project (http://www.kipi-plugins.org)
-- AUTHORS -----------------------------------------------------------
See AUTHORS file for details.
-- ABOUT -------------------------------------------------------------
Libkexiv2 is a wrapper around Exiv2 library to manipulate pictures
metadata as EXIF and IPTC.
This library is used by kipi-plugins, digiKam and others kipi host programs.
The library documentation is available on header files.
-- DEPENDENCIES -------------------------------------------------------
AutoConf >= 2.5.x http://www.gnu.org/software/autoconf
AutoMake >= 1.7.x http://www.gnu.org/software/automake
libqt >= 3.3.x http://www.trolltech.com
libkde >= 3.4.x (>=3.5.x recommended) http://www.kde.org
libexiv2 >= 0.12 (0.15 recommended) http://www.exiv2.org

@ -0,0 +1,2 @@
Last Changed Rev: 790116
Last Changed Date: 2008-03-25 22:51:54 +0100 (Tue, 25 Mar 2008)

File diff suppressed because it is too large Load Diff

881
aclocal.m4 vendored

@ -0,0 +1,881 @@
# generated automatically by aclocal 1.10.1 -*- Autoconf -*-
# Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004,
# 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
# PARTICULAR PURPOSE.
m4_ifndef([AC_AUTOCONF_VERSION],
[m4_copy([m4_PACKAGE_VERSION], [AC_AUTOCONF_VERSION])])dnl
m4_if(AC_AUTOCONF_VERSION, [2.61],,
[m4_warning([this file was generated for autoconf 2.61.
You have another version of autoconf. It may work, but is not guaranteed to.
If you have problems, you may need to regenerate the build system entirely.
To do so, use the procedure documented by the package, typically `autoreconf'.])])
# Copyright (C) 2002, 2003, 2005, 2006, 2007 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.
# AM_AUTOMAKE_VERSION(VERSION)
# ----------------------------
# Automake X.Y traces this macro to ensure aclocal.m4 has been
# generated from the m4 files accompanying Automake X.Y.
# (This private macro should not be called outside this file.)
AC_DEFUN([AM_AUTOMAKE_VERSION],
[am__api_version='1.10'
dnl Some users find AM_AUTOMAKE_VERSION and mistake it for a way to
dnl require some minimum version. Point them to the right macro.
m4_if([$1], [1.10.1], [],
[AC_FATAL([Do not call $0, use AM_INIT_AUTOMAKE([$1]).])])dnl
])
# _AM_AUTOCONF_VERSION(VERSION)
# -----------------------------
# aclocal traces this macro to find the Autoconf version.
# This is a private macro too. Using m4_define simplifies
# the logic in aclocal, which can simply ignore this definition.
m4_define([_AM_AUTOCONF_VERSION], [])
# AM_SET_CURRENT_AUTOMAKE_VERSION
# -------------------------------
# Call AM_AUTOMAKE_VERSION and AM_AUTOMAKE_VERSION so they can be traced.
# This function is AC_REQUIREd by AC_INIT_AUTOMAKE.
AC_DEFUN([AM_SET_CURRENT_AUTOMAKE_VERSION],
[AM_AUTOMAKE_VERSION([1.10.1])dnl
m4_ifndef([AC_AUTOCONF_VERSION],
[m4_copy([m4_PACKAGE_VERSION], [AC_AUTOCONF_VERSION])])dnl
_AM_AUTOCONF_VERSION(AC_AUTOCONF_VERSION)])
# AM_AUX_DIR_EXPAND -*- Autoconf -*-
# Copyright (C) 2001, 2003, 2005 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.
# For projects using AC_CONFIG_AUX_DIR([foo]), Autoconf sets
# $ac_aux_dir to `$srcdir/foo'. In other projects, it is set to
# `$srcdir', `$srcdir/..', or `$srcdir/../..'.
#
# Of course, Automake must honor this variable whenever it calls a
# tool from the auxiliary directory. The problem is that $srcdir (and
# therefore $ac_aux_dir as well) can be either absolute or relative,
# depending on how configure is run. This is pretty annoying, since
# it makes $ac_aux_dir quite unusable in subdirectories: in the top
# source directory, any form will work fine, but in subdirectories a
# relative path needs to be adjusted first.
#
# $ac_aux_dir/missing
# fails when called from a subdirectory if $ac_aux_dir is relative
# $top_srcdir/$ac_aux_dir/missing
# fails if $ac_aux_dir is absolute,
# fails when called from a subdirectory in a VPATH build with
# a relative $ac_aux_dir
#
# The reason of the latter failure is that $top_srcdir and $ac_aux_dir
# are both prefixed by $srcdir. In an in-source build this is usually
# harmless because $srcdir is `.', but things will broke when you
# start a VPATH build or use an absolute $srcdir.
#
# So we could use something similar to $top_srcdir/$ac_aux_dir/missing,
# iff we strip the leading $srcdir from $ac_aux_dir. That would be:
# am_aux_dir='\$(top_srcdir)/'`expr "$ac_aux_dir" : "$srcdir//*\(.*\)"`
# and then we would define $MISSING as
# MISSING="\${SHELL} $am_aux_dir/missing"
# This will work as long as MISSING is not called from configure, because
# unfortunately $(top_srcdir) has no meaning in configure.
# However there are other variables, like CC, which are often used in
# configure, and could therefore not use this "fixed" $ac_aux_dir.
#
# Another solution, used here, is to always expand $ac_aux_dir to an
# absolute PATH. The drawback is that using absolute paths prevent a
# configured tree to be moved without reconfiguration.
AC_DEFUN([AM_AUX_DIR_EXPAND],
[dnl Rely on autoconf to set up CDPATH properly.
AC_PREREQ([2.50])dnl
# expand $ac_aux_dir to an absolute path
am_aux_dir=`cd $ac_aux_dir && pwd`
])
# AM_CONDITIONAL -*- Autoconf -*-
# Copyright (C) 1997, 2000, 2001, 2003, 2004, 2005, 2006
# Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.
# serial 8
# AM_CONDITIONAL(NAME, SHELL-CONDITION)
# -------------------------------------
# Define a conditional.
AC_DEFUN([AM_CONDITIONAL],
[AC_PREREQ(2.52)dnl
ifelse([$1], [TRUE], [AC_FATAL([$0: invalid condition: $1])],
[$1], [FALSE], [AC_FATAL([$0: invalid condition: $1])])dnl
AC_SUBST([$1_TRUE])dnl
AC_SUBST([$1_FALSE])dnl
_AM_SUBST_NOTMAKE([$1_TRUE])dnl
_AM_SUBST_NOTMAKE([$1_FALSE])dnl
if $2; then
$1_TRUE=
$1_FALSE='#'
else
$1_TRUE='#'
$1_FALSE=
fi
AC_CONFIG_COMMANDS_PRE(
[if test -z "${$1_TRUE}" && test -z "${$1_FALSE}"; then
AC_MSG_ERROR([[conditional "$1" was never defined.
Usually this means the macro was only invoked conditionally.]])
fi])])
# Copyright (C) 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006
# Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.
# serial 9
# There are a few dirty hacks below to avoid letting `AC_PROG_CC' be
# written in clear, in which case automake, when reading aclocal.m4,
# will think it sees a *use*, and therefore will trigger all it's
# C support machinery. Also note that it means that autoscan, seeing
# CC etc. in the Makefile, will ask for an AC_PROG_CC use...
# _AM_DEPENDENCIES(NAME)
# ----------------------
# See how the compiler implements dependency checking.
# NAME is "CC", "CXX", "GCJ", or "OBJC".
# We try a few techniques and use that to set a single cache variable.
#
# We don't AC_REQUIRE the corresponding AC_PROG_CC since the latter was
# modified to invoke _AM_DEPENDENCIES(CC); we would have a circular
# dependency, and given that the user is not expected to run this macro,
# just rely on AC_PROG_CC.
AC_DEFUN([_AM_DEPENDENCIES],
[AC_REQUIRE([AM_SET_DEPDIR])dnl
AC_REQUIRE([AM_OUTPUT_DEPENDENCY_COMMANDS])dnl
AC_REQUIRE([AM_MAKE_INCLUDE])dnl
AC_REQUIRE([AM_DEP_TRACK])dnl
ifelse([$1], CC, [depcc="$CC" am_compiler_list=],
[$1], CXX, [depcc="$CXX" am_compiler_list=],
[$1], OBJC, [depcc="$OBJC" am_compiler_list='gcc3 gcc'],
[$1], UPC, [depcc="$UPC" am_compiler_list=],
[$1], GCJ, [depcc="$GCJ" am_compiler_list='gcc3 gcc'],
[depcc="$$1" am_compiler_list=])