https://bugs.kde.org/show_bug.cgi?id=295423--- Comment #23 from Kevin Kofler <
[hidden email]> ---
> Kevin what you want is a package that fail hard if a *requested* option miss a dependancy.
Unfortunately, that's not good enough (and it's a common mistake made by
developers, and in fact the whole optional dependency system in KDE gets that
wrong). The package should fail hard if I did NOT explicitly request that I
DON'T want the dependency. Everything not explicitly disabled should be
required. Otherwise, when you add some new functionality, it is still likely to
be missing in packages, because if we don't know to add the BuildRequires, we
also won't know about the -D switch to add to explicitly request the feature.
Opt-in requesting is entirely useless for packaging, we already opt in by
adding a BuildRequires to our packages, it needs to be opt-out!
I think we should probably have some "packager mode" in CMake (a -D flag we
could add to our %cmake RPM macro) where all the optional dependencies are
required unless explicitly disabled. But this is getting way out of the scope
of this bug. ;-)
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Locked
