[digiKam-users] Future of digiKam bundles...

Carlos Echenique carlos at echenique.com
Sat May 30 04:42:17 BST 2020 

Did you log out/log in to enable the integration. I use bspwm and I had to
do that. Your overrides are stored in ~/.local/share/flatpak/overrides;
this does not require sudo. Using sudo makes it system wide.
Carlos Echenique Photographer, CE Photographic

305.219.2433
<https://sgndr.live/click?redirect=tel%3A305.219.2433&dID=1590810137028&linkName=305.219.2433>
| carlos at echenique.com
Website: https://www.cephotographic.com
<https://sgndr.live/click?redirect=https%3A%2F%2Fwww.cephotographic.com&dID=1590810137028&linkName=https://www.cephotographic.com>

<https://sgndr.live/click?redirect=https%3A%2F%2Fwww.facebook.com%2Fecheniquephotos&dID=1590810137028>
<https://sgndr.live/click?redirect=https%3A%2F%2Fflickr.com%2Fphotos%2Fechenique&dID=1590810137028>
<https://sgndr.live/click?redirect=https%3A%2F%2Finstagram.com%2Fcephotographic&dID=1590810137028>


On Fri, May 29, 2020 at 11:31 PM Peter Teuben <teuben at gmail.com> wrote:

>
>     flatpak run com.github.tchx84.Flatseal
>
> I use kubuntu, and it doesn't seem to be well integrated with it, or I
> didn't install enough infrastructure to make it findable via a gui. So I
> had to do the commandline way.
>
> But before you sent this email, I googled around a bit, and I found this
> to work for me:
> sudo flatpak override org.kde.digikam --filesystem=/a7
> sudo flatpak override org.kde.digikam --filesystem=/Photos
>
>
> Especially the latter is a bit odd, since I have to symlinks in /Photos to
> /media USB drives..... weird.
>
> But to add to the confusion, those manually set directories are not stored
> in the things listed in the flatseal app. Perhaps that just "me"   (i
> didn't sudo the flatpak instlall) vs. the override , wihch required me to
> use sudo.
>
> *I can't possibly be the only one struggling with this, so we should make
> these reminders available for the flatpak newbies. *I'm sure it's all
> very powerful, but I'm still a bit underwhelmed.
>
>
> A final warning: as said, I use KDE based kubuntu, and I found flatpak is
> using ~/.var/app/org.kde.digikam/config/digikamrc and
> ~/.var/app/org.kde.digikam/config/kdeglobals
>
> I guess one could be nasty and symlink it back to your personal version in
> ~/.config, but I guess that could break if the flatpak KDE version differs
> from the system KDE version.
>
>
> peter
>
>
> PS:   in kubuntu there is a Flatpak backend that can be installed in their
> Discover tool. But surprise, surprise, you need to restart the system, so
> I'll do that some other time to continue this adventure.
>
>
> On 5/29/20 11:11 PM, Carlos Echenique wrote:
>
> Install the application flatseal (its on flathub). Launch it. You will see
> the following:
> [image: image.png]
> The highlighted part is where you add paths that you want to allow access
> to. You can see that /media and /run/media are already there. I added the
> /mnt entries for my system. Close flatseal and then launch digikam. You
> will now be able connect to the folders you desire.
> Carlos Echenique Photographer, CE Photographic
>
>
> 305.219.2433
> <https://sgndr.online/click?redirect=tel%3A305.219.2433&dID=1590808267066&linkName=305.219.2433>
> | carlos at echenique.com
> Website: https://www.cephotographic.com
> <https://sgndr.online/click?redirect=https%3A%2F%2Fwww.cephotographic.com&dID=1590808267066&linkName=https://www.cephotographic.com>
>
>
> <https://sgndr.online/click?redirect=https%3A%2F%2Fwww.facebook.com%2Fecheniquephotos&dID=1590808267066>
> <https://sgndr.online/click?redirect=https%3A%2F%2Fflickr.com%2Fphotos%2Fechenique&dID=1590808267066>
> <https://sgndr.online/click?redirect=https%3A%2F%2Finstagram.com%2Fcephotographic&dID=1590808267066>
>
>
> On Fri, May 29, 2020 at 9:37 PM Peter Teuben <teuben at gmail.com> wrote:
>
>> Can you remind us where this is done. Or an example file even better.
>>
>> On Fri, May 29, 2020, 21:28 Carlos Echenique <carlos at echenique.com>
>> wrote:
>>
>>> /media is there by default. If you regularly mount drives under /mnt
>>> just add that. You only have to do it once.
>>> Carlos Echenique Photographer, CE Photographic
>>>
>>>
>>> 305.219.2433
>>> <https://sgndr.online/click?redirect=tel%3A305.219.2433&dID=1590802086514&linkName=305.219.2433>
>>> | carlos at echenique.com
>>> Website: https://www.cephotographic.com
>>> <https://sgndr.online/click?redirect=https%3A%2F%2Fwww.cephotographic.com&dID=1590802086514&linkName=https://www.cephotographic.com>
>>>
>>>
>>> <https://sgndr.online/click?redirect=https%3A%2F%2Fwww.facebook.com%2Fecheniquephotos&dID=1590802086514>
>>> <https://sgndr.online/click?redirect=https%3A%2F%2Fflickr.com%2Fphotos%2Fechenique&dID=1590802086514>
>>> <https://sgndr.online/click?redirect=https%3A%2F%2Finstagram.com%2Fcephotographic&dID=1590802086514>
>>>
>>>
>>> On Fri, May 29, 2020 at 8:24 PM Peter Teuben <teuben at gmail.com> wrote:
>>>
>>>> I never "appreciated" these issues about both flatpak and snap.   AFAIK
>>>> appimage doesn't have this. But it really turns me off about this.
>>>>
>>>> Basically I need to give access to all mount points.  I also heard
>>>> somewhere you can use mount with the bind option, because this
>>>> micro-managing my life (e.g. popping in an external drive) is driving one
>>>> nuts.   This is not the posix file system my grandfather was using, to make
>>>> up a quote.   I can manage adding a bind option to the /etc/fstab file, but
>>>> what about my /media links.....
>>>>
>>>> thanks for clarifications, i never expected this mess.
>>>>
>>>>
>>>> peter
>>>>
>>>>
>>>>
>>>> On 5/29/20 8:01 PM, Carlos Echenique wrote:
>>>>
>>>> I used flatseal and it works as advertised. Be aware that for symlinks,
>>>> you need to grant access to the underlying path, not the symlink. To wit: I
>>>> have a Pictures directory in my home folder. Inside the pictures directory
>>>> is a symlink to a Photos folder located on another drive /mnt/data/Photos.
>>>> In order for the flatpak of digikam to be able to access via the symlink, I
>>>> had to grant it permission to access the /mnt/data/Photos folder, not the
>>>> symlink /home/user/Pictures/Photos. I entered the symlink in digikam after
>>>> that and it worked perfectly. You must do the same if you store the
>>>> database in another folder as well.
>>>> Carlos Echenique Photographer, CE Photographic
>>>>
>>>>
>>>> 305.219.2433
>>>> <https://sgndr.online/click?redirect=tel%3A305.219.2433&dID=1590796919477&linkName=305.219.2433>
>>>> | carlos at echenique.com
>>>> Website: https://www.cephotographic.com
>>>> <https://sgndr.online/click?redirect=https%3A%2F%2Fwww.cephotographic.com&dID=1590796919477&linkName=https://www.cephotographic.com>
>>>>
>>>>
>>>> <https://sgndr.online/click?redirect=https%3A%2F%2Fwww.facebook.com%2Fecheniquephotos&dID=1590796919477>
>>>> <https://sgndr.online/click?redirect=https%3A%2F%2Fflickr.com%2Fphotos%2Fechenique&dID=1590796919477>
>>>> <https://sgndr.online/click?redirect=https%3A%2F%2Finstagram.com%2Fcephotographic&dID=1590796919477>
>>>>
>>>>
>>>> On Fri, May 29, 2020 at 7:16 PM Mica Semrick <mica at silentumbrella.com>
>>>> wrote:
>>>>
>>>>> Install the application "flatseal" from flathub, then grant digikam
>>>>> access to your extra disks/filesystem location.
>>>>>
>>>>> On May 29, 2020 10:16:37 AM PDT, Peter Teuben <teuben at gmail.com>
>>>>> wrote:
>>>>>>
>>>>>> this is great news, certainly for trying out the beta.
>>>>>>
>>>>>> I do have a failure mode.  I have 7 albums in my albumRoot, 4 of those
>>>>>> will get flagged by this version and claim not to exist, eg.
>>>>>>
>>>>>> digikam.database: Folder does not exist or is not readable:
>>>>>> "/Photos/albums2"
>>>>>> digikam.database: Folder does not exist or is not readable:
>>>>>> "/a7/teuben/Pictures"
>>>>>>
>>>>>> the first one is a true symlink, but the 2nd is a real mounted
>>>>>> directory, so it's not that mount/bind issue I've seen with snaps.   If
>>>>>> I use this digikam4.db, the old digikam 6.4.0 acts worse:  it sees the
>>>>>> albums, but sees 0 photos, so starts this hours long process of
>>>>>> reloading the database. No good for me.
>>>>>>
>>>>>>
>>>>>> I guess I should try the latest appimage as well?
>>>>>>
>>>>>>
>>>>>> - peter
>>>>>>
>>>>>>
>>>>>> On 5/29/20 6:29 AM, Gilles Caulier wrote:
>>>>>>>
>>>>>>>  Done !!!
>>>>>>>
>>>>>>>  digiKam is now avaialble on FlatHub :
>>>>>>>
>>>>>>>  https://flathub.org/apps/details/org.kde.digikam
>>>>>>>
>>>>>>>  Best
>>>>>>>
>>>>>>>  Gilles Caulier
>>>>>>>
>>>>>>>  Le lun. 25 mai 2020 à 17:49, Gilles Caulier <caulier.gilles at gmail.com> a écrit :
>>>>>>>>
>>>>>>>>  Look like digiKam will be also added to official FlatHub repository soon :
>>>>>>>>
>>>>>>>>  https://github.com/flathub/flathub/pull/1544#pullrequestreview-417884061
>>>>>>>>
>>>>>>>>  Gilles Caulier
>>>>>>>>
>>>>>>>>  Le lun. 25 mai 2020 à 15:09, Gilles Caulier <caulier.gilles at gmail.com> a écrit :
>>>>>>>>>
>>>>>>>>>  Hi,
>>>>>>>>>
>>>>>>>>>  Another important point : the Flatpak do not include yet the
>>>>>>>>>  application translations files. It's relevant by the missing
>>>>>>>>>  sunversion executable on the KDE server.
>>>>>>>>>
>>>>>>>>>  And yes, all translations team from KDE project still to use
>>>>>>>>>  subversion to host i18n data.
>>>>>>>>>
>>>>>>>>>  As whole KDE migrate progressively from an own git/svn servers to
>>>>>>>>>  gitlab, i read that i18n will also migrate to git in the near future.
>>>>>>>>>  So wait and see...
>>>>>>>>>
>>>>>>>>>  Best
>>>>>>>>>
>>>>>>>>>  Gilles Caulier
>>>>>>>>>
>>>>>>>>>  Le lun. 25 mai 2020 à 12:04, Gilles Caulier <caulier.gilles at gmail.com> a écrit :
>>>>>>>>>>
>>>>>>>>>>  Hi,
>>>>>>>>>>
>>>>>>>>>>  I just updated the Flatpak notice page on digikam source repository :
>>>>>>>>>>
>>>>>>>>>>  https://invent.kde.org/graphics/digikam/-/tree/master/project/bundles/flatpak
>>>>>>>>>>
>>>>>>>>>>  digiKam Flatpak is now compiled with ALL non-deprecated options,
>>>>>>>>>>  including Web services using KIO. Look like the application resume is
>>>>>>>>>>  well documented now, with plenty of screenshots.
>>>>>>>>>>
>>>>>>>>>>  By non deprecated, i want mean the 2 ones : Baloo and Akonady
>>>>>>>>>>  supports. Both make a mess with digiKam (especially Baloo).
>>>>>>>>>>
>>>>>>>>>>  As i read, Flatpak is able to notify users when a new version is
>>>>>>>>>>  published. I don't yet verified if it work well.
>>>>>>>>>>
>>>>>>>>>>  On Flatpak, it's possible to rate and review the application. So don't
>>>>>>>>>>  hesitate to promote the application.
>>>>>>>>>>
>>>>>>>>>>  My best
>>>>>>>>>>
>>>>>>>>>>  Gilles Caulier
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>  Le dim. 24 mai 2020 à 12:24, Gilles Caulier <caulier.gilles at gmail.com> a écrit :
>>>>>>>>>>>
>>>>>>>>>>>  Hi all users,
>>>>>>>>>>>
>>>>>>>>>>>  I would to give some feedback about the digiKam bundles migration advance...
>>>>>>>>>>>
>>>>>>>>>>>  The current files provided by the project are listed below :
>>>>>>>>>>>
>>>>>>>>>>>  - Linux AppImage 64 bits
>>>>>>>>>>>  - Linux AppImage 32 bits
>>>>>>>>>>>  - Macos Package installer 64 bits (based on Macports)
>>>>>>>>>>>  - Windows installer 64 bits (compiled with MXE - MinGW)
>>>>>>>>>>>  - Windows installer 32 bits (compiled with MXE - MinGW)
>>>>>>>>>>>
>>>>>>>>>>>  Current problems for these bundles are listed below :
>>>>>>>>>>>
>>>>>>>>>>>  - AppImage : not signed, do not support KIO extensions, do not support
>>>>>>>>>>>  ICU (language extension), not published on official repository.
>>>>>>>>>>>  - MacOS package : It's not relocatable, even if MacOS support well
>>>>>>>>>>>  this feature. I don't found the time to finalize yet the install
>>>>>>>>>>>  relocation support in bash script. Package is not published on MacOS
>>>>>>>>>>>  store.
>>>>>>>>>>>  - MXE Windows installer : not signed, not published on Windows store.
>>>>>>>>>>>  Do not support KIO extension.
>>>>>>>>>>>
>>>>>>>>>>>  But we have a new one starting to work and i working on : FlatPak
>>>>>>>>>>>
>>>>>>>>>>>  This one is signed, published of official repository automatically
>>>>>>>>>>>  (you can install it on Discover application for ex). It support ICU
>>>>>>>>>>>  and KIO too... FlatPak is compiled on KDE infrastructure nightly and
>>>>>>>>>>>  automatically. Only a 64 bits version is supported.
>>>>>>>>>>>
>>>>>>>>>>>  This want mean that AppImage end of life is near. We will still
>>>>>>>>>>>  publish officially the AppImage until 7.0.0, but later, if FlatPak do
>>>>>>>>>>>  the job as well, AppImage will be dropped...
>>>>>>>>>>>
>>>>>>>>>>>  For Windows, all the digiKam code compile fine under Microsoft Visual
>>>>>>>>>>>  C++ compiler. This is the goal to obtain a signed and published
>>>>>>>>>>>  version on Microsoft store. You can imagine that Microsoft will only
>>>>>>>>>>>  support the official Windows compiler, and not GCC to permit to sign
>>>>>>>>>>>  and publish application on the store. Don't forget, Microsoft is well
>>>>>>>>>>>  Closed Source (:=))))
>>>>>>>>>>>
>>>>>>>>>>>  Microsoft compiler is just the hell. It slow and require a Windows
>>>>>>>>>>>  operating system. The current cross compilation solution that we use
>>>>>>>>>>>  work fully under Linux, and compilation time are reduced by 4/5 ! A
>>>>>>>>>>>  full Linux Workflow is a non virus guaranty !
>>>>>>>>>>>
>>>>>>>>>>>  The Visual C++ workflow is also only available on 64 bits and is
>>>>>>>>>>>  computed on KDE infrastructure, but the installer compilation is
>>>>>>>>>>>  broken due to a weird configuration on KDE infrastructure. I currently
>>>>>>>>>>>  try to found a work around.
>>>>>>>>>>>
>>>>>>>>>>>  Personalty, i don't want to left MXE solution for the moment.
>>>>>>>>>>>
>>>>>>>>>>>  For MacOS, the KDE infrastructure based on Craft compilation framework
>>>>>>>>>>>  will be a solution to sing and publish a relocatable package for
>>>>>>>>>>>  Apple. digiKam do not compile yet due to  missing dependencies.
>>>>>>>>>>>
>>>>>>>>>>>  Voilà, i hope to be enough clear with these technical points.
>>>>>>>>>>>
>>>>>>>>>>>  My best
>>>>>>>>>>>
>>>>>>>>>>>  Gilles Caulier
>>>>>>>>>>
>>>>>>>>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20200529/55e973e7/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 195203 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20200529/55e973e7/attachment-0001.png>

More information about the Digikam-users mailing list