Bug 242405 - Digikam configure script misleading.
Summary: Digikam configure script misleading.
Status: RESOLVED NOT A BUG
Alias: None
Product: digikam
Classification: Applications
Component: Portability-Cmake (show other bugs)
Version: 1.3.0
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-21 21:01 UTC by Evert Vorster
Modified: 2022-01-23 05:03 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 7.6.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Evert Vorster 2010-06-21 21:01:26 UTC
Version:           1.3.0 (using KDE 4.4.4) 
OS:                Linux

Digikam 1.3.0 depends upon unreleased versions of libraries libkexiv2 and libkdcraw. When the configure script does not find the version of the libraries it needs, it reports the libraries missing, in stead of too old.

Reproducible: Didn't try

Steps to Reproduce:
Compile digikam 1.3.0

Actual Results:  
Misleading messages from the configure script:
-- checking for module 'libkdcraw>=1.1.0'
--   package 'libkdcraw>=1.1.0' not found
-- checking for module 'libkexiv2>=1.1.0'
--   package 'libkexiv2>=1.1.0' not found


Expected Results:  
"Your installed versions of $LIBRARY is too old, please upgrade to at least $REQUIRED version"

It's poor form to release software as "stable" when it depends upon libraries that have not yet been marked as stable.
Comment 1 Johannes Wienke 2010-06-21 21:07:43 UTC
We cannot do much about this because the pkgconfig macro from cmake simply says whether it has found a suitable version or not. If not, it does not tell which version was found but wasn't sufficient.
Comment 2 Evert Vorster 2010-06-21 21:48:48 UTC
Thanks for the extra info. 

I was under the impression that each project can fine-tune their own cmake script, same as the configure script of old. Do you think we can ask for a change in the cmake scripts themselves, then?

-Evert-
Comment 3 Johannes Wienke 2010-06-21 21:54:28 UTC
We could do a workaround, first requesting every version of the library and then in a second step the desired version. But I do not think it's worth the work.

Actually I think it would be better if kde would switch to the new cmake pkgconfig wrapper. This one gives much better console output of what's exactly requested.
Comment 4 Evert Vorster 2010-06-21 21:56:56 UTC
Nope. I prefer to keep things simple as well. 

It would be better for the pkgconfig wrapper to be used in KDE.