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

[Peter Teuben]

Can you remind us where this is done. Or an example file even better. 

On Fri, May 29, 2020, 21:28 Carlos Echenique <[hidden email]> wrote:

/media is there by default. If you regularly mount drives under /mnt just add that. You only have to do it once.

On Fri, May 29, 2020 at 8:24 PM Peter Teuben <[hidden email]> 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 | [hidden email] Website: https://www.cephotographic.com

On Fri, May 29, 2020 at 7:16 PM Mica Semrick <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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

[etrigan63]

Install the application flatseal (its on flathub). Launch it. You will see the following:

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.

On Fri, May 29, 2020 at 9:37 PM Peter Teuben <[hidden email]> wrote:

Can you remind us where this is done. Or an example file even better. 

On Fri, May 29, 2020, 21:28 Carlos Echenique <[hidden email]> 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 | [hidden email] Website: https://www.cephotographic.com

On Fri, May 29, 2020 at 8:24 PM Peter Teuben <[hidden email]> 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 | [hidden email] Website: https://www.cephotographic.com

On Fri, May 29, 2020 at 7:16 PM Mica Semrick <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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

[Peter Teuben]

    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:

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.

On Fri, May 29, 2020 at 9:37 PM Peter Teuben <[hidden email]> wrote:

Can you remind us where this is done. Or an example file even better. 

On Fri, May 29, 2020, 21:28 Carlos Echenique <[hidden email]> 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 | [hidden email] Website: https://www.cephotographic.com

On Fri, May 29, 2020 at 8:24 PM Peter Teuben <[hidden email]> 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 | [hidden email] Website: https://www.cephotographic.com

On Fri, May 29, 2020 at 7:16 PM Mica Semrick <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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

[etrigan63]

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.

On Fri, May 29, 2020 at 11:31 PM Peter Teuben <[hidden email]> 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:

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 | [hidden email] Website: https://www.cephotographic.com

On Fri, May 29, 2020 at 9:37 PM Peter Teuben <[hidden email]> wrote:

Can you remind us where this is done. Or an example file even better. 

On Fri, May 29, 2020, 21:28 Carlos Echenique <[hidden email]> 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 | [hidden email] Website: https://www.cephotographic.com

On Fri, May 29, 2020 at 8:24 PM Peter Teuben <[hidden email]> 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 | [hidden email] Website: https://www.cephotographic.com

On Fri, May 29, 2020 at 7:16 PM Mica Semrick <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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

[Peter Teuben]

haha, you made me look at the bswm youtube, this is quite something.

I'll add your overrides to my writeup.

On 5/29/20 11:42 PM, Carlos Echenique wrote:

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.

On Fri, May 29, 2020 at 11:31 PM Peter Teuben <[hidden email]> 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:

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 | [hidden email] Website: https://www.cephotographic.com

On Fri, May 29, 2020 at 9:37 PM Peter Teuben <[hidden email]> wrote:

Can you remind us where this is done. Or an example file even better. 

On Fri, May 29, 2020, 21:28 Carlos Echenique <[hidden email]> 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 | [hidden email] Website: https://www.cephotographic.com

On Fri, May 29, 2020 at 8:24 PM Peter Teuben <[hidden email]> 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 | [hidden email] Website: https://www.cephotographic.com

On Fri, May 29, 2020 at 7:16 PM Mica Semrick <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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

[Stuart T Rogers]

Interesting this flatseal, just installed it and opened it up but it
does not show the override I have used to access my home directory which
allows Digikam to see my database and photo directories!

Also as I said before it's a real pain that I am unable to access easily
any other apps like GIMP, I guess unless they are installed using
flatpak. Probably some way to do it but this all just seems total
overkill in order to run Digikam.

I simply cannot see a reason to run it locked down like this. Yes there
are things where it would be very useful because there is real danger
but not this. I'll stick to appimage (assuming it continues) or wait for
the distro RPM.

Stuart



--
Website: https://www.stella-maris.org.uk
or:      https//www.broadstairs.org

[etrigan63]

How did you add the override? Flatseal stores them in .local/share/flatpak/overrides not in the system in order to maintain the sandbox.

On Sat, May 30, 2020 at 5:53 AM Stuart T Rogers <[hidden email]> wrote:

Interesting this flatseal, just installed it and opened it up but it
does not show the override I have used to access my home directory which
allows Digikam to see my database and photo directories!

Also as I said before it's a real pain that I am unable to access easily
any other apps like GIMP, I guess unless they are installed using
flatpak. Probably some way to do it but this all just seems total
overkill in order to run Digikam.

I simply cannot see a reason to run it locked down like this. Yes there
are things where it would be very useful because there is real danger
but not this. I'll stick to appimage (assuming it continues) or wait for
the distro RPM.

Stuart



--
Website: https://www.stella-maris.org.uk
or:      https//www.broadstairs.org

[Stuart T Rogers]

I used the flatpak override filesystem command in a console window.

Stuart

On 31 May 2020 01:01:56 BST, Carlos Echenique <[hidden email]> wrote:

>How did you add the override? Flatseal stores them in
>.local/share/flatpak/overrides not in the system in order to maintain
>the
>sandbox.
>Carlos Echenique Photographer, CE Photographic
>
>305.219.2433 | [hidden email]
>Website: https://www.cephotographic.com
><https://www.facebook.com/echeniquephotos>
><https://flickr.com/photos/echenique>
><https://instagram.com/cephotographic>
>
>
>On Sat, May 30, 2020 at 5:53 AM Stuart T Rogers
><[hidden email]>
>wrote:
>
>> Interesting this flatseal, just installed it and opened it up but it
>> does not show the override I have used to access my home directory
>which
>> allows Digikam to see my database and photo directories!
>>
>> Also as I said before it's a real pain that I am unable to access
>easily
>> any other apps like GIMP, I guess unless they are installed using
>> flatpak. Probably some way to do it but this all just seems total
>> overkill in order to run Digikam.
>>
>> I simply cannot see a reason to run it locked down like this. Yes
>there
>> are things where it would be very useful because there is real danger
>> but not this. I'll stick to appimage (assuming it continues) or wait
>for
>> the distro RPM.
>>
>> Stuart
>>
>>
>>
>> --
>> Website: https://www.stella-maris.org.uk
>> or:      https//www.broadstairs.org
>>

--
Sent from my Samsung Galaxy J5 with K-9 Mail. Please excuse my brevity.

[etrigan63]

Hmmm. The implementation of flatpak support is specific to the distro being used. I am using a spin of an Arch-based distro and that is where the files are placed on my system. YMMV.

Carlos Echenique
CE Photography
[hidden email]

On May 31, 2020, 2:34 AM -0400, Stuart Rogers <[hidden email]>, wrote:

I used the flatpak override filesystem command in a console window.

Stuart

On 31 May 2020 01:01:56 BST, Carlos Echenique <[hidden email]> wrote:

How did you add the override? Flatseal stores them in
.local/share/flatpak/overrides not in the system in order to maintain
the
sandbox.
Carlos Echenique Photographer, CE Photographic

305.219.2433 | [hidden email]
Website: https://www.cephotographic.com
<https://www.facebook.com/echeniquephotos>
<https://flickr.com/photos/echenique>
<https://instagram.com/cephotographic>


On Sat, May 30, 2020 at 5:53 AM Stuart T Rogers
<[hidden email]>
wrote:

Interesting this flatseal, just installed it and opened it up but it
does not show the override I have used to access my home directory

which

allows Digikam to see my database and photo directories!

Also as I said before it's a real pain that I am unable to access

easily

any other apps like GIMP, I guess unless they are installed using
flatpak. Probably some way to do it but this all just seems total
overkill in order to run Digikam.

I simply cannot see a reason to run it locked down like this. Yes

there

are things where it would be very useful because there is real danger
but not this. I'll stick to appimage (assuming it continues) or wait

for

the distro RPM.

Stuart



--
Website: https://www.stella-maris.org.uk
or: https//www.broadstairs.org

--
Sent from my Samsung Galaxy J5 with K-9 Mail. Please excuse my brevity.

[Brad Rogers]

On Sun, 31 May 2020 15:48:58 -0400
Cirrus <[hidden email]> wrote:

Hello Cirrus,

>There's no unsubscribe info in the emails, so I'm clueless.

As always, with a mailman list, it's in the headers:

List-Unsubscribe: <https://mail.kde.org/mailman/options/digikam-users>,
 <mailto:[hidden email]?subject=unsubscribe>

--
 Regards  _
         / )           "The blindingly obvious is
        / _)rad        never immediately apparent"
You only see me for the clothes that I wear
Public Image - Public Image Ltd

[Peter Teuben]

i ran into another beautiful feature of the flatpak.....   I wanted to
edit a file with another app, gimp, but its not inthe list, since it can
only look inside of it container (without going through contortions).
Even /usr/bin/gimp doesn't work.

I dunno about flatpak.

On 5/31/20 9:32 AM, Carlos Echenique wrote:

> Hmmm. The implementation of flatpak support is specific to the distro
> being used. I am using a spin of an Arch-based distro and that is
> where the files are placed on my system. YMMV.
>
> Carlos Echenique
> CE Photography
> [hidden email]
> On May 31, 2020, 2:34 AM -0400, Stuart Rogers
> <[hidden email]>, wrote:
>> I used the flatpak override filesystem command in a console window.
>>
>> Stuart
>>
>> On 31 May 2020 01:01:56 BST, Carlos Echenique <[hidden email]>
>> wrote:
>>> How did you add the override? Flatseal stores them in
>>> .local/share/flatpak/overrides not in the system in order to maintain
>>> the
>>> sandbox.
>>> Carlos Echenique Photographer, CE Photographic
>>>
>>> 305.219.2433 | [hidden email]
>>> Website: https://www.cephotographic.com
>>> <https://www.facebook.com/echeniquephotos>
>>> <https://flickr.com/photos/echenique>
>>> <https://instagram.com/cephotographic>
>>>
>>>
>>> On Sat, May 30, 2020 at 5:53 AM Stuart T Rogers
>>> <[hidden email]>
>>> wrote:
>>>
>>>> Interesting this flatseal, just installed it and opened it up but it
>>>> does not show the override I have used to access my home directory
>>> which
>>>> allows Digikam to see my database and photo directories!
>>>>
>>>> Also as I said before it's a real pain that I am unable to access
>>> easily
>>>> any other apps like GIMP, I guess unless they are installed using
>>>> flatpak. Probably some way to do it but this all just seems total
>>>> overkill in order to run Digikam.
>>>>
>>>> I simply cannot see a reason to run it locked down like this. Yes
>>> there
>>>> are things where it would be very useful because there is real danger
>>>> but not this. I'll stick to appimage (assuming it continues) or wait
>>> for
>>>> the distro RPM.
>>>>
>>>> Stuart
>>>>
>>>>
>>>>
>>>> --
>>>> Website: https://www.stella-maris.org.uk
>>>> or: https//www.broadstairs.org
>>>>
>>
>> --
>> Sent from my Samsung Galaxy J5 with K-9 Mail. Please excuse my brevity.

[etrigan63]

Flatseal to the rescue, Peter.

Carlos Echenique
CE Photography
[hidden email]

On May 31, 2020, 9:03 PM -0400, Peter Teuben <[hidden email]>, wrote:

i ran into another beautiful feature of the flatpak.....   I wanted to
edit a file with another app, gimp, but its not inthe list, since it can
only look inside of it container (without going through contortions).
Even /usr/bin/gimp doesn't work.

I dunno about flatpak.

On 5/31/20 9:32 AM, Carlos Echenique wrote:

Hmmm. The implementation of flatpak support is specific to the distro
being used. I am using a spin of an Arch-based distro and that is
where the files are placed on my system. YMMV.

Carlos Echenique
CE Photography
[hidden email]
On May 31, 2020, 2:34 AM -0400, Stuart Rogers
<[hidden email]>, wrote:

I used the flatpak override filesystem command in a console window.

Stuart

On 31 May 2020 01:01:56 BST, Carlos Echenique <[hidden email]>
wrote:

How did you add the override? Flatseal stores them in
.local/share/flatpak/overrides not in the system in order to maintain
the
sandbox.
Carlos Echenique Photographer, CE Photographic

305.219.2433 | [hidden email]
Website: https://www.cephotographic.com
<https://www.facebook.com/echeniquephotos>
<https://flickr.com/photos/echenique>
<https://instagram.com/cephotographic>


On Sat, May 30, 2020 at 5:53 AM Stuart T Rogers
<[hidden email]>
wrote:

Interesting this flatseal, just installed it and opened it up but it
does not show the override I have used to access my home directory

which

allows Digikam to see my database and photo directories!

Also as I said before it's a real pain that I am unable to access

easily

any other apps like GIMP, I guess unless they are installed using
flatpak. Probably some way to do it but this all just seems total
overkill in order to run Digikam.

I simply cannot see a reason to run it locked down like this. Yes

there

are things where it would be very useful because there is real danger
but not this. I'll stick to appimage (assuming it continues) or wait

for

the distro RPM.

Stuart



--
Website: https://www.stella-maris.org.uk
or: https//www.broadstairs.org

--
Sent from my Samsung Galaxy J5 with K-9 Mail. Please excuse my brevity.

[Peter Teuben]

I know.... again. but this is getting tiring.

On 5/31/20 9:06 PM, Carlos Echenique wrote:

> Flatseal to the rescue, Peter.
>
> Carlos Echenique
> CE Photography
> [hidden email]
> On May 31, 2020, 9:03 PM -0400, Peter Teuben <[hidden email]>, wrote:
>> i ran into another beautiful feature of the flatpak.....   I wanted to
>> edit a file with another app, gimp, but its not inthe list, since it can
>> only look inside of it container (without going through contortions).
>> Even /usr/bin/gimp doesn't work.
>>
>> I dunno about flatpak.
>>
>> On 5/31/20 9:32 AM, Carlos Echenique wrote:
>>> Hmmm. The implementation of flatpak support is specific to the distro
>>> being used. I am using a spin of an Arch-based distro and that is
>>> where the files are placed on my system. YMMV.
>>>
>>> Carlos Echenique
>>> CE Photography
>>> [hidden email]
>>> On May 31, 2020, 2:34 AM -0400, Stuart Rogers
>>> <[hidden email]>, wrote:
>>>> I used the flatpak override filesystem command in a console window.
>>>>
>>>> Stuart
>>>>
>>>> On 31 May 2020 01:01:56 BST, Carlos Echenique <[hidden email]>
>>>> wrote:
>>>>> How did you add the override? Flatseal stores them in
>>>>> .local/share/flatpak/overrides not in the system in order to maintain
>>>>> the
>>>>> sandbox.
>>>>> Carlos Echenique Photographer, CE Photographic
>>>>>
>>>>> 305.219.2433 | [hidden email]
>>>>> Website: https://www.cephotographic.com
>>>>> <https://www.facebook.com/echeniquephotos>
>>>>> <https://flickr.com/photos/echenique>
>>>>> <https://instagram.com/cephotographic>
>>>>>
>>>>>
>>>>> On Sat, May 30, 2020 at 5:53 AM Stuart T Rogers
>>>>> <[hidden email]>
>>>>> wrote:
>>>>>
>>>>>> Interesting this flatseal, just installed it and opened it up but it
>>>>>> does not show the override I have used to access my home directory
>>>>> which
>>>>>> allows Digikam to see my database and photo directories!
>>>>>>
>>>>>> Also as I said before it's a real pain that I am unable to access
>>>>> easily
>>>>>> any other apps like GIMP, I guess unless they are installed using
>>>>>> flatpak. Probably some way to do it but this all just seems total
>>>>>> overkill in order to run Digikam.
>>>>>>
>>>>>> I simply cannot see a reason to run it locked down like this. Yes
>>>>> there
>>>>>> are things where it would be very useful because there is real danger
>>>>>> but not this. I'll stick to appimage (assuming it continues) or wait
>>>>> for
>>>>>> the distro RPM.
>>>>>>
>>>>>> Stuart
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Website: https://www.stella-maris.org.uk
>>>>>> or: https//www.broadstairs.org
>>>>>>
>>>>
>>>> --
>>>> Sent from my Samsung Galaxy J5 with K-9 Mail. Please excuse my brevity.

Le 01/06/2020 à 03:06, Carlos Echenique a écrit :
> Flatseal to the rescue, Peter.
>

you should understand that most new software do not take in account new
users.

I had to search half an hour to understand that flatpak kde software
install is "discover" (never heard before of this sift)

and there I could install flatseal, unknown in yast (I use openSUSE 15.1)

thanks
jdd

--
http://dodin.org

[Stuart T Rogers]

I'm sorry but I do feel that flatpak is a complete waste of time, there
are so many hoops to jump through to get digikam working as most users
want and need that it is a wasted effort. Also probably most users would
enable access to everything in order to be able to use apps they already
have installed, thus completely negating the whole point of a sandbox!

I very much doubt that anyone anywhere in the world has had a security
issue directly caused by digikam so to have to run it sandboxed like
this is a completely pointless. I have not had any problems with
appimage to test beta versions and my distros RPM works perfectly with
immediate access to everything I need accessible. Also being a rolling
release I get the latest stable releases very quickly.

Yes there probably are apps I would want to run sandboxed, if I needed
them, but they are very few and far between and frankly none that I have
seen so far available in flatpak.

Yes you need to use Discover in openSUSE to do the installs etc and so
far there is no access from YAST. Discover can be used to install normal
openSUSE programs as well so it may become the norm in future, although
personally I prefer YAST or commandline.

Stuart

On 01/06/2020 06:13, [hidden email] wrote:

> Le 01/06/2020 à 03:06, Carlos Echenique a écrit :
>> Flatseal to the rescue, Peter.
>>
>
> you should understand that most new software do not take in account new
> users.
>
> I had to search half an hour to understand that flatpak kde software
> install is "discover" (never heard before of this sift)
>
> and there I could install flatseal, unknown in yast (I use openSUSE 15.1)
>
> thanks
> jdd
>

--
Website: https://www.stella-maris.org.uk
or:      https//www.broadstairs.org

[Gilles Caulier-4]

Hi all,

Sorry for my late response in the thread, but i'm not at home
actually, and busy in familly

I start to group all information around Flatpak in a README.md file
from git repository, here :

https://invent.kde.org/graphics/digikam/-/tree/master/project/bundles/flatpak

There are plenty of details to append in the file due to the feedback
here. Please use gitlab, fork the repository, and send a pull request.

With gitlab, it's very simple, and ALL can be done with web interface.
README.md file can be edited on line too...

Thanks in advance for your contributions.

Best

Gilles Caulier

Le lun. 1 juin 2020 à 10:22, Stuart T Rogers
<[hidden email]> a écrit :

>
> I'm sorry but I do feel that flatpak is a complete waste of time, there
> are so many hoops to jump through to get digikam working as most users
> want and need that it is a wasted effort. Also probably most users would
> enable access to everything in order to be able to use apps they already
> have installed, thus completely negating the whole point of a sandbox!
>
> I very much doubt that anyone anywhere in the world has had a security
> issue directly caused by digikam so to have to run it sandboxed like
> this is a completely pointless. I have not had any problems with
> appimage to test beta versions and my distros RPM works perfectly with
> immediate access to everything I need accessible. Also being a rolling
> release I get the latest stable releases very quickly.
>
> Yes there probably are apps I would want to run sandboxed, if I needed
> them, but they are very few and far between and frankly none that I have
> seen so far available in flatpak.
>
> Yes you need to use Discover in openSUSE to do the installs etc and so
> far there is no access from YAST. Discover can be used to install normal
> openSUSE programs as well so it may become the norm in future, although
> personally I prefer YAST or commandline.
>
> Stuart
>
> On 01/06/2020 06:13, [hidden email] wrote:
> > Le 01/06/2020 à 03:06, Carlos Echenique a écrit :
> >> Flatseal to the rescue, Peter.
> >>
> >
> > you should understand that most new software do not take in account new
> > users.
> >
> > I had to search half an hour to understand that flatpak kde software
> > install is "discover" (never heard before of this sift)
> >
> > and there I could install flatseal, unknown in yast (I use openSUSE 15.1)
> >
> > thanks
> > jdd
> >
>
> --
> Website: https://www.stella-maris.org.uk
> or:      https//www.broadstairs.org

[Chris Green]

>
> With gitlab, it's very simple, and ALL can be done with web interface.

... and why is that any better than command line? :-)  I use the
command line for almost everything I do, including installing
software. Anything that is GUI only is not a lot of use to me, and I
don't believe I'm completely alone in this.

--
Chris Green

[Gilles Caulier-4]

Hi,

No problem with CLI, but i would to see more and more contributor
writing doc, notice, tuto. Using the web interface is a way to
contribute quickly and easily, without to know all development
bulldozers...

Best

Gilles caulier

Le lun. 1 juin 2020 à 13:27, Chris Green <[hidden email]> a écrit :

>
> >
> > With gitlab, it's very simple, and ALL can be done with web interface.
>
> ... and why is that any better than command line? :-)  I use the
> command line for almost everything I do, including installing
> software. Anything that is GUI only is not a lot of use to me, and I
> don't believe I'm completely alone in this.
>
> --
> Chris Green

[Gilles Caulier-4]

Q : Someone can check if translations are embedded well in the digiKam
FlatPak bundle...

I have a doubt as AppImage is more larger than FlatPak, and i'm sure
that AppImage bundle includes all translation files.

Best

Gilles Caulier

Le lun. 1 juin 2020 à 11:04, Gilles Caulier <[hidden email]> a écrit :

>
> Hi all,
>
> Sorry for my late response in the thread, but i'm not at home
> actually, and busy in familly
>
> I start to group all information around Flatpak in a README.md file
> from git repository, here :
>
> https://invent.kde.org/graphics/digikam/-/tree/master/project/bundles/flatpak
>
> There are plenty of details to append in the file due to the feedback
> here. Please use gitlab, fork the repository, and send a pull request.
>
> With gitlab, it's very simple, and ALL can be done with web interface.
> README.md file can be edited on line too...
>
> Thanks in advance for your contributions.
>
> Best
>
> Gilles Caulier
>
> Le lun. 1 juin 2020 à 10:22, Stuart T Rogers
> <[hidden email]> a écrit :
> >
> > I'm sorry but I do feel that flatpak is a complete waste of time, there
> > are so many hoops to jump through to get digikam working as most users
> > want and need that it is a wasted effort. Also probably most users would
> > enable access to everything in order to be able to use apps they already
> > have installed, thus completely negating the whole point of a sandbox!
> >
> > I very much doubt that anyone anywhere in the world has had a security
> > issue directly caused by digikam so to have to run it sandboxed like
> > this is a completely pointless. I have not had any problems with
> > appimage to test beta versions and my distros RPM works perfectly with
> > immediate access to everything I need accessible. Also being a rolling
> > release I get the latest stable releases very quickly.
> >
> > Yes there probably are apps I would want to run sandboxed, if I needed
> > them, but they are very few and far between and frankly none that I have
> > seen so far available in flatpak.
> >
> > Yes you need to use Discover in openSUSE to do the installs etc and so
> > far there is no access from YAST. Discover can be used to install normal
> > openSUSE programs as well so it may become the norm in future, although
> > personally I prefer YAST or commandline.
> >
> > Stuart
> >
> > On 01/06/2020 06:13, [hidden email] wrote:
> > > Le 01/06/2020 à 03:06, Carlos Echenique a écrit :
> > >> Flatseal to the rescue, Peter.
> > >>
> > >
> > > you should understand that most new software do not take in account new
> > > users.
> > >
> > > I had to search half an hour to understand that flatpak kde software
> > > install is "discover" (never heard before of this sift)
> > >
> > > and there I could install flatseal, unknown in yast (I use openSUSE 15.1)
> > >
> > > thanks
> > > jdd
> > >
> >
> > --
> > Website: https://www.stella-maris.org.uk
> > or:      https//www.broadstairs.org

[digikam-2]

On Mon, 1 Jun 2020 09:22:01 +0100
Stuart T Rogers <[hidden email]> wrote:

> I'm sorry but I do feel that flatpak is a complete waste of time,
> there are so many hoops to jump through to get digikam working as
> most users want and need that it is a wasted effort. Also probably
> most users would enable access to everything in order to be able to
> use apps they already have installed, thus completely negating the
> whole point of a sandbox!

I disagree with you.

1. Creating a flatpak digikam does not mean that you will not be able
to get it from your own distribution, if you are using Linux,
whatever your distribution does.

2. Earlier, Gilles said that it takes him a huge amount of time to
build and rebuild the appimages. If some other infrastructure can
do it for him, this will mean that he will have more time to spend on:
making dk even better or "having a life" or...

Gilles is one of the main driving force behind DK, we have to trust
him and his judgment. Thanks Gilles.


--
sknahT

vyS