[Digikam-users] digikam 4.9.0 binary packages for OS X

Account, Listserv listaccount at revenant.org
Fri Apr 17 05:18:22 BST 2015

Gilles and Veaceslav -- First, I appreciate your years of work on the
digikam project. Thank you.

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.

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.

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.

Please let me know if you have questions.


On Thu, Apr 16, 2015 at 3:29 PM, Gilles Caulier <caulier.gilles at gmail.com>

> Shanti,
> thanks to share your experience.
> I would to know more your your bin packaging workflow under OSX. I use
> MacBook pro here, so, if your host your script in digiKam git
> repository, i will able to build bin package for next version
> Your script must be documented. A text file is enough to host with
> script. We need to know all dependencies, settings, OSX-XCode-macports
> version to use, etc...
> Q : how did you solve KDE run time dependency with you package. For
> ex, digiKam still to use KIO-Slave. How did you package it ?
> Gilles Caulier
> 2015-04-16 21:12 GMT+02:00 Veaceslav Munteanu <
> veaceslav.munteanu90 at gmail.com>:
> > Hello,
> >
> > good work.
> >
> > I guess we can but your packaging scripts on the git, since we also
> > have different bootstrap stripts for different linux distribution.
> >
> > Having them on the git, somebody else can pick them up and improve, if
> needed.
> >
> > Veaceslav
> >
> > On Thu, Apr 16, 2015 at 8:51 PM, Account, Listserv
> > <listaccount at revenant.org> wrote:
> >> I have assembled two digikam 4.9.0 binary packages for OS X, including
> >> external MySQL database support. They were made using bash/python
> scripts to
> >> build it from MacPorts in a a virtual machine. One was built with a
> +debug
> >> variant, the other isn't.
> >>
> >> I've seen regular requests for OS X binary packages on the web page and
> this
> >> list, as well as complaints about the length/complexity/reliability of
> >> building digikam with MacPorts. So I figure I should share -- if you
> would
> >> like to test them, email me directly and I'll send you a link.
> >>
> >> I'm not posting links to the list for two reasons. First, I don't want
> >> someone to just grab and install binary packages, expecting a stable,
> >> official digikam release, instead of a risky bastardized derivation that
> >> I've cobbled together. I'm not a coder. This is my first crack at
> packaging
> >> a MacOS application. The build/package scripts include "rm -rf" but not
> >> error checking.  My testing has been limited to opening digikam and
> >> showfoto, looking through my photos, and some photo manipulations.  Some
> >> photographs I rotated using my digikam 4.0.0 package were corrupted -- I
> >> don't know if that was due to my packaging. Anyone who is testing the
> >> packages or scripts should be very cautious -- back up the photos and
> the
> >> computer it's running on, test it in a VM, etc..
> >>
> >> Second, I don't think I'll have time to properly support OS X binary
> >> releases. From what I can tell, properly scripting this build and
> package
> >> process would have been be simple for someone who knows what they're
> doing.
> >> Due obligations and lack of skill, it's taken me over a year of
> intermittent
> >> work to make my clumsy scripts. I likely won't have time or skill to fix
> >> problems. If you notice something's not right (e.g. why won't the
> packaged
> >> versions use Aqua widgets?) you'll have to investigate and fix it
> yourself
> >> (then share the answer hopefully).
> >>
> >> All that said, email me off-list if you understand my cautions and are
> >> interested in testing -- and improving upon -- what I've put together.
> >>
> >> Shanti
> >>
> >> _______________________________________________
> >> Digikam-users mailing list
> >> Digikam-users at kde.org
> >> https://mail.kde.org/mailman/listinfo/digikam-users
> >>
> > _______________________________________________
> > Digikam-users mailing list
> > Digikam-users at kde.org
> > https://mail.kde.org/mailman/listinfo/digikam-users
> _______________________________________________
> Digikam-users mailing list
> Digikam-users at kde.org
> https://mail.kde.org/mailman/listinfo/digikam-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20150416/5bc43f43/attachment.html>

More information about the Digikam-users mailing list