[digiKam-users] The future of 6.0.0 bundles and C++11 support...

[Dan Kaczor]

Among the many reasons some of us have switched from Windows to Linux
was the ability to preserve older investments in computer hardware. We
have 6 computers currently in the house, only 2 are Windows, 1 is a
laptop with Windows x64. The other 4 computers are running 32 bit Linux
of various OS's. We also get donated old computers from people. We make
some simple refurbishments, install Linux (usually Mint 17+ or 18) and
put Digikam on all of them then give them to families and the elderly
who cannot afford computers.

So I vote not to drop Digikam 32 bits. Otherwise we will stop updating
Digikam at whatever version 32 bits support is ended.

Dan
Using Digikam since 2.5 (I think)

[AndriusWild]

Would it be possible to compile 32bit versions of digiKam 6+ at all? If it is possible but is too much work it might worth to try compiling 32bit version once in a while, e.g. 6.0.0. and then 6.9.0 or whichever is the last version in 6 series.

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Dan Kaczor <[hidden email]>

Date: 2018-04-01 1:26 PM (GMT-07:00)

To: [hidden email]

Subject: [digiKam-users] The future of 6.0.0 bundles and C++11 support...

Among the many reasons some of us have switched from Windows to Linux
was the ability to preserve older investments in computer hardware. We
have 6 computers currently in the house, only 2 are Windows, 1 is a
laptop with Windows x64. The other 4 computers are running 32 bit Linux
of various OS's. We also get donated old computers from people. We make
some simple refurbishments, install Linux (usually Mint 17+ or 18) and
put Digikam on all of them then give them to families and the elderly
who cannot afford computers.

So I vote not to drop Digikam 32 bits. Otherwise we will stop updating
Digikam at whatever version 32 bits support is ended.

Dan
Using Digikam since 2.5 (I think)

[Gilles Caulier-4]

Did you real well my original mail ?

I never speak about the non compatibility of whole digiKam and 32 bits support. I speak only about bundles, and especially the AppImage compiled under CentoOS 6.9 for binary compatibility reasons.

The linux distro packages in 32 bits can be available. After all the code is free to use. You can also compile the code yourself if all puzzle parts are present on your 32 bits system : compiler, shared libs, etc...

Best

Gilles Caulier

2018-04-01 22:34 GMT+02:00 Andrey Goreev <[hidden email]>:

Would it be possible to compile 32bit versions of digiKam 6+ at all? If it is possible but is too much work it might worth to try compiling 32bit version once in a while, e.g. 6.0.0. and then 6.9.0 or whichever is the last version in 6 series.

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Dan Kaczor <[hidden email]>

Date: 2018-04-01 1:26 PM (GMT-07:00)

To: [hidden email]

Subject: [digiKam-users] The future of 6.0.0 bundles and C++11 support...

Among the many reasons some of us have switched from Windows to Linux
was the ability to preserve older investments in computer hardware. We
have 6 computers currently in the house, only 2 are Windows, 1 is a
laptop with Windows x64. The other 4 computers are running 32 bit Linux
of various OS's. We also get donated old computers from people. We make
some simple refurbishments, install Linux (usually Mint 17+ or 18) and
put Digikam on all of them then give them to families and the elderly
who cannot afford computers.

So I vote not to drop Digikam 32 bits. Otherwise we will stop updating
Digikam at whatever version 32 bits support is ended.

Dan
Using Digikam since 2.5 (I think)

[AndriusWild]

Well, if compiling the 32 bit appimage in your CentoOS became overwhelming I think there is no other way but stop doing that and let someone else compile the 32bit packages.

I took a look at what distributions support 32 bit still. There are not that many of them left. But Fedora is still there. Its packages are usually very up to date so there is a big chance that they might keep compiling digikam 6+ for 32 bit systems

On Sun, Apr 1, 2018 at 3:18 PM, Gilles Caulier <[hidden email]> wrote:

Did you real well my original mail ?

I never speak about the non compatibility of whole digiKam and 32 bits support. I speak only about bundles, and especially the AppImage compiled under CentoOS 6.9 for binary compatibility reasons.

The linux distro packages in 32 bits can be available. After all the code is free to use. You can also compile the code yourself if all puzzle parts are present on your 32 bits system : compiler, shared libs, etc...

Best

Gilles Caulier

2018-04-01 22:34 GMT+02:00 Andrey Goreev <[hidden email]>:

Would it be possible to compile 32bit versions of digiKam 6+ at all? If it is possible but is too much work it might worth to try compiling 32bit version once in a while, e.g. 6.0.0. and then 6.9.0 or whichever is the last version in 6 series.

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Dan Kaczor <[hidden email]>

Date: 2018-04-01 1:26 PM (GMT-07:00)

To: [hidden email]

Subject: [digiKam-users] The future of 6.0.0 bundles and C++11 support...

Among the many reasons some of us have switched from Windows to Linux
was the ability to preserve older investments in computer hardware. We
have 6 computers currently in the house, only 2 are Windows, 1 is a
laptop with Windows x64. The other 4 computers are running 32 bit Linux
of various OS's. We also get donated old computers from people. We make
some simple refurbishments, install Linux (usually Mint 17+ or 18) and
put Digikam on all of them then give them to families and the elderly
who cannot afford computers.

So I vote not to drop Digikam 32 bits. Otherwise we will stop updating
Digikam at whatever version 32 bits support is ended.

Dan
Using Digikam since 2.5 (I think)

[AndriusWild]

Here is a good resource to find 32 bit digikam RPMs 

https://rpmfind.net/linux/rpm2html/search.php?query=digikam

On Sun, Apr 1, 2018 at 5:55 PM, Andrey Goreev <[hidden email]> wrote:

Well, if compiling the 32 bit appimage in your CentoOS became overwhelming I think there is no other way but stop doing that and let someone else compile the 32bit packages.

I took a look at what distributions support 32 bit still. There are not that many of them left. But Fedora is still there. Its packages are usually very up to date so there is a big chance that they might keep compiling digikam 6+ for 32 bit systems

On Sun, Apr 1, 2018 at 3:18 PM, Gilles Caulier <[hidden email]> wrote:

Did you real well my original mail ?

I never speak about the non compatibility of whole digiKam and 32 bits support. I speak only about bundles, and especially the AppImage compiled under CentoOS 6.9 for binary compatibility reasons.

The linux distro packages in 32 bits can be available. After all the code is free to use. You can also compile the code yourself if all puzzle parts are present on your 32 bits system : compiler, shared libs, etc...

Best

Gilles Caulier

2018-04-01 22:34 GMT+02:00 Andrey Goreev <[hidden email]>:

Would it be possible to compile 32bit versions of digiKam 6+ at all? If it is possible but is too much work it might worth to try compiling 32bit version once in a while, e.g. 6.0.0. and then 6.9.0 or whichever is the last version in 6 series.

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Dan Kaczor <[hidden email]>

Date: 2018-04-01 1:26 PM (GMT-07:00)

To: [hidden email]

Subject: [digiKam-users] The future of 6.0.0 bundles and C++11 support...

Among the many reasons some of us have switched from Windows to Linux
was the ability to preserve older investments in computer hardware. We
have 6 computers currently in the house, only 2 are Windows, 1 is a
laptop with Windows x64. The other 4 computers are running 32 bit Linux
of various OS's. We also get donated old computers from people. We make
some simple refurbishments, install Linux (usually Mint 17+ or 18) and
put Digikam on all of them then give them to families and the elderly
who cannot afford computers.

So I vote not to drop Digikam 32 bits. Otherwise we will stop updating
Digikam at whatever version 32 bits support is ended.

Dan
Using Digikam since 2.5 (I think)

[Remco Viëtor]

On dimanche 1 avril 2018 21:26:27 CEST Dan Kaczor wrote:

> Among the many reasons some of us have switched from Windows to Linux
> was the ability to preserve older investments in computer hardware. We
> have 6 computers currently in the house, only 2 are Windows, 1 is a
> laptop with Windows x64. The other 4 computers are running 32 bit Linux
> of various OS's. We also get donated old computers from people. We make
> some simple refurbishments, install Linux (usually Mint 17+ or 18) and
> put Digikam on all of them then give them to families and the elderly
> who cannot afford computers.
>
> So I vote not to drop Digikam 32 bits. Otherwise we will stop updating
> Digikam at whatever version 32 bits support is ended.
>
> Dan
> Using Digikam since 2.5 (I think)

I don't know how old those computers are, but I've been using 64-bit Linux
since quite a number of years (long enough that upgrading my previous computer
wasn't possible anymore as the interfaces had changed). Linux Mint 18 exists
in a 64-bit version.

And as Gilles remarked, you can always switch to compiling Digikam yourself.
Though that can get progressively more difficult if the distributions start
phasing out otherwise unused libraries Digikam needs.

Remco

Le 02/04/2018 à 08:23, Remco Viëtor a écrit :

> And as Gilles remarked, you can always switch to compiling Digikam yourself.
> Though that can get progressively more difficult if the distributions start
> phasing out otherwise unused libraries Digikam needs.
>

chance are any 32 bits distro will have digikam. Only the appimage may
be more difficult to find, but brand new functions often ask more of the
hardware so needs more recent computer

on openSUSE, Tumbleweed is still proposed with 32 bits (although this
may not be for anybody)

jdd


--
http://dodin.org

[Gilles Caulier-4]

Hi all, 

Yesterday evening, i tried to build 6.0.0 AppImage under CentoS 6.9 in 64 bits. I forget another piece which increase the compilation complexity : ffmpeg.

digiKam require ffmpeg 3.x. Centos has no ffmpeg rpm officially, excepted one contrib repo in Romania with a 2.x release outdated.

We have already a file in bugzilla to build digiKam +qtAv with a recent ffmpeg, in goal to be able to manage recent video containers as H265. So i must add rules to compile ffmpeg myself in the bundle, and it's a complex task. I cannot use static ffmpeg build here, as i need shared libs.

So, no way to build 32 bits AppImage bundles for the future...

Gilles Caulier

2018-04-02 8:30 GMT+02:00 [hidden email] <[hidden email]>:

Le 02/04/2018 à 08:23, Remco Viëtor a écrit :

And as Gilles remarked, you can always switch to compiling Digikam yourself.
Though that can get progressively more difficult if the distributions start
phasing out otherwise unused libraries Digikam needs.

chance are any 32 bits distro will have digikam. Only the appimage may be more difficult to find, but brand new functions often ask more of the hardware so needs more recent computer

on openSUSE, Tumbleweed is still proposed with 32 bits (although this may not be for anybody)

jdd


--
http://dodin.org

[Gilles Caulier-4]

Hi all,

Done : https://bugs.kde.org/show_bug.cgi?id=384807

Now ffmpeg 3.3.6 is integrated in Linux AppImage 64 bits for incoming 6.0.0 release.

The new beta AppImage 6.0.0 will be available soon at usual place. 

https://www.flickr.com/photos/digikam/41139912022/in/dateposted/

Take a care to use it : it's really a beta, do not use yet in production !!!!

Best

Gilles Caulier

2018-04-02 9:08 GMT+02:00 Gilles Caulier <[hidden email]>:

Hi all, 

Yesterday evening, i tried to build 6.0.0 AppImage under CentoS 6.9 in 64 bits. I forget another piece which increase the compilation complexity : ffmpeg.

digiKam require ffmpeg 3.x. Centos has no ffmpeg rpm officially, excepted one contrib repo in Romania with a 2.x release outdated.

We have already a file in bugzilla to build digiKam +qtAv with a recent ffmpeg, in goal to be able to manage recent video containers as H265. So i must add rules to compile ffmpeg myself in the bundle, and it's a complex task. I cannot use static ffmpeg build here, as i need shared libs.

So, no way to build 32 bits AppImage bundles for the future...

Gilles Caulier

2018-04-02 8:30 GMT+02:00 [hidden email] <[hidden email]>:

Le 02/04/2018 à 08:23, Remco Viëtor a écrit :

And as Gilles remarked, you can always switch to compiling Digikam yourself.
Though that can get progressively more difficult if the distributions start
phasing out otherwise unused libraries Digikam needs.

chance are any 32 bits distro will have digikam. Only the appimage may be more difficult to find, but brand new functions often ask more of the hardware so needs more recent computer

on openSUSE, Tumbleweed is still proposed with 32 bits (although this may not be for anybody)

jdd


--
http://dodin.org

[AndriusWild]

Hello Gilles

Here is the compilation guide:

https://trac.ffmpeg.org/wiki/CompilationGuide/Centos

I have used it on openSUSE and have compiled ffmpeg without an issue.

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Gilles Caulier <[hidden email]>

Date: 2018-04-02 1:08 AM (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: [digiKam-users] The future of 6.0.0 bundles and C++11 support...

Hi all, 

Yesterday evening, i tried to build 6.0.0 AppImage under CentoS 6.9 in 64 bits. I forget another piece which increase the compilation complexity : ffmpeg.

digiKam require ffmpeg 3.x. Centos has no ffmpeg rpm officially, excepted one contrib repo in Romania with a 2.x release outdated.

We have already a file in bugzilla to build digiKam +qtAv with a recent ffmpeg, in goal to be able to manage recent video containers as H265. So i must add rules to compile ffmpeg myself in the bundle, and it's a complex task. I cannot use static ffmpeg build here, as i need shared libs.

So, no way to build 32 bits AppImage bundles for the future...

Gilles Caulier

2018-04-02 8:30 GMT+02:00 [hidden email] <[hidden email]>:

Le 02/04/2018 à 08:23, Remco Viëtor a écrit :

And as Gilles remarked, you can always switch to compiling Digikam yourself.
Though that can get progressively more difficult if the distributions start
phasing out otherwise unused libraries Digikam needs.

chance are any 32 bits distro will have digikam. Only the appimage may be more difficult to find, but brand new functions often ask more of the hardware so needs more recent computer

on openSUSE, Tumbleweed is still proposed with 32 bits (although this may not be for anybody)

jdd


--
http://dodin.org

[AndriusWild]

Thanks Gilles!

I will give it a try for sure.

I want to test the import function specifically.

Hopefully video files' dates will be recognized correctly. 

If the import works I won't need Rapid Photo Downloader anymore.

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Gilles Caulier <[hidden email]>

Date: 2018-04-02 8:01 AM (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: [digiKam-users] The future of 6.0.0 bundles and C++11 support...

Hi all,

Done : https://bugs.kde.org/show_bug.cgi?id=384807

Now ffmpeg 3.3.6 is integrated in Linux AppImage 64 bits for incoming 6.0.0 release.

The new beta AppImage 6.0.0 will be available soon at usual place. 

https://www.flickr.com/photos/digikam/41139912022/in/dateposted/

Take a care to use it : it's really a beta, do not use yet in production !!!!

Best

Gilles Caulier

2018-04-02 9:08 GMT+02:00 Gilles Caulier <[hidden email]>:

Hi all, 

Yesterday evening, i tried to build 6.0.0 AppImage under CentoS 6.9 in 64 bits. I forget another piece which increase the compilation complexity : ffmpeg.

digiKam require ffmpeg 3.x. Centos has no ffmpeg rpm officially, excepted one contrib repo in Romania with a 2.x release outdated.

We have already a file in bugzilla to build digiKam +qtAv with a recent ffmpeg, in goal to be able to manage recent video containers as H265. So i must add rules to compile ffmpeg myself in the bundle, and it's a complex task. I cannot use static ffmpeg build here, as i need shared libs.

So, no way to build 32 bits AppImage bundles for the future...

Gilles Caulier

2018-04-02 8:30 GMT+02:00 [hidden email] <[hidden email]>:

Le 02/04/2018 à 08:23, Remco Viëtor a écrit :

And as Gilles remarked, you can always switch to compiling Digikam yourself.
Though that can get progressively more difficult if the distributions start
phasing out otherwise unused libraries Digikam needs.

chance are any 32 bits distro will have digikam. Only the appimage may be more difficult to find, but brand new functions often ask more of the hardware so needs more recent computer

on openSUSE, Tumbleweed is still proposed with 32 bits (although this may not be for anybody)

jdd


--
http://dodin.org

[Gilles Caulier-4]

2018-04-02 16:22 GMT+02:00 Andrey Goreev <[hidden email]>:

Thanks Gilles!

I will give it a try for sure.

I want to test the import function specifically.

Hopefully video files' dates will be recognized correctly.

 

yes the date is taken from video metadata now, and not only this information. All important data to populate DB from video file in fact.

The goal is to perform search of video based on capture settings, when it's possible. It's diffciult because video Exif is partially implemented in camera.

If information are backported in digiKam from video metadata, all appears in XMP namespaces. You will see this view fully populated by the ffmpeg parser that i write.

Gilles Caulier