On 10 January 2012 02:12, brad <span dir="ltr"><<a href="mailto:bkn@ithryn.net">bkn@ithryn.net</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><div>phil,</div><div><br></div><div>were you running previous digikam versions? Did you completely uninstall the macports version of digikam? perhaps you're loading old libraries from a previous installation of digikam. Or, perhaps the digikam.rc file is causing problems. </div>
<div>try,</div><div> mv ~/Library/Preferences/KDE/share/apps/digikam ~/Library/Preferences/KDE/share/apps/digikam.old</div><div>then try launching digikam</div><div><br></div><div>With regards the the .shell files, those are scripts generated by cmake in an attempt to setup your environment to make launching the application easier. If applications launch fine without the .shell then just use the straight binaries. </div>
<div><br></div><div>cheers,</div><span class="HOEnZb"><font color="#888888"> - brad</font></span><div><br><br></div></div>
<br></blockquote></div><br><br>
Brad, thanks for your mails, sorry for tardy replies but work gets in the way of fun sometimes .....!<br><br>Re previous versions of Digikam - <br>Yes
I did uninstall the version I was running under MacPorts. There are
older, 'inactive' ones still on the system, but MacPorts normally seems
pretty good at tidying up - inactive ports are just there in case you do
want to activate them again, and executables & libraries are
normally removed from any paths. <br><br>The tip about renaming the rc file was useful - on the Mac this is <br>~/Library/Preferences/KDE/share/config/digikamrc
(not .rc) and there's also a
~/Library/Preferences/KDE/share/apps/digikam directory, which in my case
just had a cameras.xml file in it.<br><br>I moved both of them sideways
and restarted Digikam (the 2.6 git build) from the terminal - this time
I did get the 'first time' config windows coming up; then of course it
started the 'QKqueueFileSystemWatcherEngine::addPaths: open: Too many
open files' errors before bombing out on some other issues. <br><br>Re this 'too many open files' issue in <a href="https://bugs.kde.org/show_bug.cgi?id=289330">https://bugs.kde.org/show_bug.cgi?id=289330</a> - <br>
I'm
still a bit unclear there; is it some new feature / behaviour in
Digikam post 2.3 that's now causing this MacOS 'files per process'
limit to be reached? I've tried with various versions of qt (4.7.2 -
4.7.4) and it doesn't make any difference. <br><br>I saw re the albumwatch.patch file but my knowledge doesn't extend to knowing where or how to apply that!<br><br>In terms of my strategy now - <br>It would seem to be sensible for me to try and get a known-working version (2.3 from what you say) up and running. <br>
<br>I
failed to work out how to use git to get a known and released digikam
version back from
<a href="https://projects.kde.org/projects/extragear/graphics/digikam/digikam-software-compilation/repository">https://projects.kde.org/projects/extragear/graphics/digikam/digikam-software-compilation/repository</a> <br>
<br>That is probably my lack of knowledge about git of course.<br><br>I
also wasn't clear on what the difference was between the above URL and
<a href="https://projects.kde.org/projects/extragear/graphics/digikam/repository">https://projects.kde.org/projects/extragear/graphics/digikam/repository</a><br><br>My
final attempt last night was to try and see if I could get things to
work by downloading the tarball from
<a href="http://sourceforge.net/projects/digikam/files/digikam/2.3.0/">http://sourceforge.net/projects/digikam/files/digikam/2.3.0/</a><br><br>I
unpacked that, and the directories looked similar to what I'd got back
using git (for the 2.6 development release) so I followed the
instructions I had done before, in <a href="https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/entry/README.MACOSX" target="_blank">https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/entry/README.MACOSX</a><br>
<br>However, that fell at the first hurdle, when I ran the ./download-repos script it fell over - <br><br>---------<br><span style="font-family:courier new,monospace">$ ./download-repos</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace">sh: line 0: cd: core/.git/hooks: No such file or directory</span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">sh: line 0: cd: extra/libkface/.git/hooks: No such file or directory</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace">sh: line 0: cd: extra/libkgeomap/.git/hooks: No such file or directory</span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">sh: line 0: cd: extra/kipi-plugins/.git/hooks: No such file or directory</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace">sh: line 0: cd: extra/libkexiv2/.git/hooks: No such file or directory</span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">sh: line 0: cd: extra/libkdcraw/.git/hooks: No such file or directory</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace">sh: line 0: cd: extra/libkipi/.git/hooks: No such file or directory</span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">sh: line 0: cd: extra/libksane/.git/hooks: No such file or directory</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace">sh: line 0: cd: extra/libmediawiki/.git/hooks: No such file or directory</span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">sh: line 0: cd: extra/libkvkontakte/.git/hooks: No such file or directory</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace">sh: line 0: cd: doc/digikam/.git/hooks: No such file or directory</span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">sh: line 0: cd: doc/kipi-plugins/.git/hooks: No such file or directory</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace">sh: line 0: cd: .git/hooks: No such file or directory</span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">sh: kdialog: command not found</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace">sh: kdialog: command not found</span><br style="font-family:courier new,monospace"><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">**** l10n ****</span><br style="font-family:courier new,monospace">
<br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">./project/release/fetch_l10n.rb:33:in `mkdir': File exists - po (Errno::EEXIST)</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace"> from ./project/release/fetch_l10n.rb:33</span><br><br><br>---------<br><br>Indeed, there is no '.git/hooks' under any of the dirs it mentions. <br>At that point I decided it was all too hard, and definitely past my bedtime!<br>
<br>I
would still like to crack this issue of not having to rely on the
Macports version getting updated by the supporter - even though that is
by far the simplest way of getting things working! Having prodded quite
a bit with people's help, with a bit more understanding (and learning
on my part!) I feel it ought to be achievable!<br><br>So if there are
still any further hints to be had re either getting hold of a specific
Digikam release under git, or on how to make the tarball work on
MacOS, I would be grateful ........<br><br>Cheers<br>Phil<br><br><br><br>