<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
I too would like to thank Gilles and Veachslav and everyone that has
ever worked on digiKam. I have been using it since 2007 and except
for a couple of unstable versions, it's positively the BEST photo
management program ever written. <br>
<br>
I manage almost a million photos in digiKam. I have a dual Xeon 8
core computer running Debian and 16MB RAM. I hope one day digiKam
can take advantage of all those cores.<br>
<br>
There's nothing out there that comes close to the capabilities of
digiKam. <br>
<br>
Thank you all. Keep up the great work.<br>
<br>
Jeff<br>
<br>
<div class="moz-cite-prefix">Account, Listserv wrote:<br>
</div>
<blockquote
cite="mid:CAOL18NOPNTF-CwVjce=To5Cd2DwNGjP2sUVsUumZnmRRBmC2+g@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>Gilles and Veaceslav -- First, I appreciate your years of
work on the digikam project. Thank you.<br>
<br>
In response to Gilles' question: The packaging script uses a
staging directory to hold files actually needed to run
digikam and the other applications. I made a list through
trial and error, of libraries, configuration files, icons,
etc. which otool couldn't identify but which should be
included. These include the runtime libraries, or at least
the ones whose absence caused a problem that I noticed (e.g.
the qtmysql library). I manually added them to the list
files to be run through the dependency lister and copied to
the package. <br>
<br>
I presume that manually listing files for inclusion will
cause the script or finished packages to break whenever the
runtime dependencies change. But I'm not aware of any
automated way to prepare that list.<br>
<br>
</div>
I sent you links to download the scripts, after adding some
comments. Hopefully those and the readme will provide enough
explanation to be comprehensible. I don't mind if you put them
on the git repository if that would be useful, but I suggest
they should be sanity-checked by someone who knows what
they're doing first. <br>
<br>
Please let me know if you have questions.<br>
<br>
</div>
Shanti<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Apr 16, 2015 at 3:29 PM, Gilles
Caulier <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:caulier.gilles@gmail.com" target="_blank">caulier.gilles@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Shanti,<br>
<br>
thanks to share your experience.<br>
<br>
I would to know more your your bin packaging workflow under
OSX. I use<br>
MacBook pro here, so, if your host your script in digiKam
git<br>
repository, i will able to build bin package for next
version<br>
<br>
Your script must be documented. A text file is enough to
host with<br>
script. We need to know all dependencies, settings,
OSX-XCode-macports<br>
version to use, etc...<br>
<br>
Q : how did you solve KDE run time dependency with you
package. For<br>
ex, digiKam still to use KIO-Slave. How did you package it ?<br>
<span class="HOEnZb"><font color="#888888"><br>
Gilles Caulier<br>
</font></span>
<div class="HOEnZb">
<div class="h5"><br>
2015-04-16 21:12 GMT+02:00 Veaceslav Munteanu <<a
moz-do-not-send="true"
href="mailto:veaceslav.munteanu90@gmail.com">veaceslav.munteanu90@gmail.com</a>>:<br>
> Hello,<br>
><br>
> good work.<br>
><br>
> I guess we can but your packaging scripts on the
git, since we also<br>
> have different bootstrap stripts for different
linux distribution.<br>
><br>
> Having them on the git, somebody else can pick them
up and improve, if needed.<br>
><br>
> Veaceslav<br>
><br>
> On Thu, Apr 16, 2015 at 8:51 PM, Account, Listserv<br>
> <<a moz-do-not-send="true"
href="mailto:listaccount@revenant.org">listaccount@revenant.org</a>>
wrote:<br>
>> I have assembled two digikam 4.9.0 binary
packages for OS X, including<br>
>> external MySQL database support. They were made
using bash/python scripts to<br>
>> build it from MacPorts in a a virtual machine.
One was built with a +debug<br>
>> variant, the other isn't.<br>
>><br>
>> I've seen regular requests for OS X binary
packages on the web page and this<br>
>> list, as well as complaints about the
length/complexity/reliability of<br>
>> building digikam with MacPorts. So I figure I
should share -- if you would<br>
>> like to test them, email me directly and I'll
send you a link.<br>
>><br>
>> I'm not posting links to the list for two
reasons. First, I don't want<br>
>> someone to just grab and install binary
packages, expecting a stable,<br>
>> official digikam release, instead of a risky
bastardized derivation that<br>
>> I've cobbled together. I'm not a coder. This is
my first crack at packaging<br>
>> a MacOS application. The build/package scripts
include "rm -rf" but not<br>
>> error checking. My testing has been limited to
opening digikam and<br>
>> showfoto, looking through my photos, and some
photo manipulations. Some<br>
>> photographs I rotated using my digikam 4.0.0
package were corrupted -- I<br>
>> don't know if that was due to my packaging.
Anyone who is testing the<br>
>> packages or scripts should be very cautious --
back up the photos and the<br>
>> computer it's running on, test it in a VM,
etc..<br>
>><br>
>> Second, I don't think I'll have time to
properly support OS X binary<br>
>> releases. From what I can tell, properly
scripting this build and package<br>
>> process would have been be simple for someone
who knows what they're doing.<br>
>> Due obligations and lack of skill, it's taken
me over a year of intermittent<br>
>> work to make my clumsy scripts. I likely won't
have time or skill to fix<br>
>> problems. If you notice something's not right
(e.g. why won't the packaged<br>
>> versions use Aqua widgets?) you'll have to
investigate and fix it yourself<br>
>> (then share the answer hopefully).<br>
>><br>
>> All that said, email me off-list if you
understand my cautions and are<br>
>> interested in testing -- and improving upon --
what I've put together.<br>
>><br>
>> Shanti<br>
>><br>
>> _______________________________________________<br>
>> Digikam-users mailing list<br>
>> <a moz-do-not-send="true"
href="mailto:Digikam-users@kde.org">Digikam-users@kde.org</a><br>
>> <a moz-do-not-send="true"
href="https://mail.kde.org/mailman/listinfo/digikam-users"
target="_blank">https://mail.kde.org/mailman/listinfo/digikam-users</a><br>
>><br>
> _______________________________________________<br>
> Digikam-users mailing list<br>
> <a moz-do-not-send="true"
href="mailto:Digikam-users@kde.org">Digikam-users@kde.org</a><br>
> <a moz-do-not-send="true"
href="https://mail.kde.org/mailman/listinfo/digikam-users"
target="_blank">https://mail.kde.org/mailman/listinfo/digikam-users</a><br>
_______________________________________________<br>
Digikam-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:Digikam-users@kde.org">Digikam-users@kde.org</a><br>
<a moz-do-not-send="true"
href="https://mail.kde.org/mailman/listinfo/digikam-users"
target="_blank">https://mail.kde.org/mailman/listinfo/digikam-users</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Digikam-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Digikam-users@kde.org">Digikam-users@kde.org</a>
<a class="moz-txt-link-freetext" href="https://mail.kde.org/mailman/listinfo/digikam-users">https://mail.kde.org/mailman/listinfo/digikam-users</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
"Everything you've ever wanted is on the other side of fear." -George Addair
</pre>
</body>
</html>