<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body><div>Jono,</div><div><br></div><div>There are plenty of linux distributions that have the latest stable digikam in their repos.</div><div><br></div><div>KDE Neon</div><div>openSUSE (Tumbleweed for sure, I don't know about Leap)</div><div>Fedora</div><div>Manjaro / Arch</div><div>etc.</div><div><br></div><div>Maybe the distro you have chosen isn't quite corresponding your needs? I was in the same boat a couple of years ago...</div><div><br></div><div id="composer_signature"><div style="font-size:85%;color:#575757" dir="auto">Sent from my Samsung Galaxy smartphone.</div></div><div><br></div><div style="font-size:100%;color:#000000"><!-- originalMessage --><div>-------- Original message --------</div><div>From: Jono pollard <jono.pollard@gmail.com> </div><div>Date: 2018-08-18 5:40 PM (GMT-07:00) </div><div>To: digiKam - Home Manage your photographs as a professional with the power of open source <digikam-users@kde.org> </div><div>Subject: Re: [digiKam-users] appimage </div><div><br></div></div><div dir="ltr">Thanks for the suggestion and that's I guess what I'll have to do, but that's my whole point. That it's a more involved process than either sudo dpkg -i digikam.deb or apt-get install digikam. Either of those just does everything for you. No need to create new directories to store stuff, no adding things to your PATH. I don't even know what a .desktop file is. If this is simpler and easier for the user, why is it more involved? I get why it's easier for devs to create but it certainly isn't easier for users. I'm not new to linux, I've been using it solely on my personal laptop for maybe 5 years and before that I was using it off and on, dual boot or on an extra machine since like 2002. I'm not an "(advanced) Linux user" by any means but I'm no stranger. And making things more difficult never seems like progress to me.<div><br></div><div>Jono</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Aug 18, 2018 at 4:26 PM, Mica Semrick <span dir="ltr"><<a href="mailto:mica@silentumbrella.com" target="_blank">mica@silentumbrella.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>If you put all your appimages in one folder, like ~/Applications, you can either add that to your path, or you can create .desktop files for each application. That will get them recognized by most launchers.<br>
<br>
Some appimages check for their own .desktop file and make one for you if it doesn't exist. This is how the gimp appimages works.<span class="HOEnZb"><font color="#888888"><br>
<br>
-m</font></span><div><div class="h5"><br><br><div class="gmail_quote">On August 18, 2018 11:33:34 AM PDT, Jono pollard <<a href="mailto:jono.pollard@gmail.com" target="_blank">jono.pollard@gmail.com</a>> wrote:<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">All I can say is that at least flatpack easily integrates into the rest of the system. Appimage is more like windows or mac where you can just run a program from where ever. Which can obviously be convenient but it's a nightmare when literally every other program is well integrated into the system. You guys do whatever you like, I'm just letting you know as a user what the experience is like. And it ain't ideal. I think sometimes devs forget that regular people are going to be using the stuff they spend so much time and effort on. Thought I'd offer a little feedback. Like I said previously, I am a big fan of the software in general and appreciate what you guys do.<div><br></div><div>Jono</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Aug 18, 2018 at 10:13 AM, Gilles Caulier <span dir="ltr"><<a 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"><div><div dir="auto">Flat pack vs AppImage : this is a good question</div></div><div dir="auto"><br></div><div dir="auto">2 years ago I was contacted by the AppImage Lead developer to propose a digikam bundle</div><div dir="auto"><br></div><div dir="auto">I this tile I was already take a look to the bundles for Linux. Flatpack was not really documented and AppImage very well. With the help of AppImage, the Rita team which already provide an AppImage bundle I created a first version in 3 weeks with the minimum features. Since this time I create a lots of bash scripts to create the bundles with a good documentation. This include also windows with a cross compilation through mixe, and macOS using Mac ports. </div><div dir="auto"><br></div><div dir="auto">Flatpack is more mature now and more secure from the start to send box the application better than AppImage.</div><div dir="auto">AppImage has now the same concept, so there is no more advantage to use flatpack.</div><div dir="auto"><br></div><div dir="auto">So I will not investigate to create a flatpack version of DK. If someone want to do it, no problem, but I maintain the AppImage and my time is limited</div><div dir="auto"><br></div><div dir="auto">Other important point : keep provide a bundle factory including AppImage, windows installer and Mac package</div><div dir="auto">This use step by step the craft framework. This can be fine for small applications, but for digikam we need something we’ll customized.</div><div dir="auto"><br></div><div dir="auto"><div><a href="https://binary-factory.kde.org/" target="_blank">https://binary-factory.kde.org<wbr>/</a></div><div dir="auto"><br></div><div dir="auto">Perhaps, in the future, we will use this service, but for the moment, the do scripts do the job well since a very long time, where craft framework still under development ( I receive the mails from the team)</div><div dir="auto"><br></div><div dir="auto">Voilà for this story. Packaging is complex job and take a while, but a complex application badly packaged cannot work properly and finally, users will report the application as completely bugous.</div><div dir="auto"><br></div><div dir="auto">Gilles caulier</div><br></div><div class="m_3764280398871330793HOEnZb"><div class="m_3764280398871330793h5"><div><br><div class="gmail_quote"><div dir="ltr">Le sam. 18 août 2018 à 17:22, <<a href="mailto:digikam@911networks.com" target="_blank">digikam@911networks.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Sat, 18 Aug 2018 14:35:12 +0200<br>
Gilles Caulier <<a href="mailto:caulier.gilles@gmail.com" target="_blank">caulier.gilles@gmail.com</a>> wrote:<br>
<br>
> So to resume :<br>
> <br>
> 1/ I support AppImage<br>
> 2/ I will continuous to support AppImage in the future.<br>
> 3/ If you don't like AppImage, ask to your packagers to update and<br>
> support digiKam application natively in your system, because we<br>
> (digiKam team) don't it instead.<br>
<br>
I like the principle of appimage. It allows me to use DK. Currently,<br>
I'm on xfce. It makes my life simple.<br>
<br>
Question to Gilles:<br>
<br>
appimage vs flatpak.<br>
<br>
More and more are using flatpak to include everything. My son, in<br>
academia/bioinfomatics requires that people send their software in<br>
"flatpaks" which is becoming quite well accepted in academia.<br>
<br>
BTW, Isn't GIMP also using flatpak with Redhat supporting the project?<br>
<br>
-- <br>
sknahT<br>
<br>
vyS<br>
</blockquote></div></div></div></div><span class="m_3764280398871330793HOEnZb"><font color="#888888">-- <br><div dir="ltr" class="m_3764280398871330793m_-7287773057361002262gmail_signature" data-smartmail="gmail_signature">Send with Gmail Mobile</div>
</font></span></blockquote></div><br></div>
</blockquote></div></div></div></div></blockquote></div><br></div>
</body></html>