
pcre is actually still in use by kjs.
Removing it runs the risk of subtle breakages, see also the upstream notice [1].
However, `pcre` 1.x is insecure and unmaintained and should be removed.
With plasma 5 being scheduled for removal,
the breakages caused by removing pcre from kjs should be non-critical.
[1] 3c663ad8ac/CMakeLists.txt (L36-46)
25 lines
515 B
Nix
25 lines
515 B
Nix
{
|
|
lib,
|
|
mkDerivation,
|
|
extra-cmake-modules,
|
|
kdoctools,
|
|
qtbase,
|
|
}:
|
|
|
|
mkDerivation {
|
|
pname = "kjs";
|
|
nativeBuildInputs = [
|
|
extra-cmake-modules
|
|
kdoctools
|
|
];
|
|
buildInputs = [
|
|
qtbase
|
|
];
|
|
cmakeFlags = [
|
|
# this can break stuff, see:
|
|
# https://invent.kde.org/frameworks/kjs/-/blob/3c663ad8ac16f8982784a5ebd5d9200e7aa07936/CMakeLists.txt#L36-46
|
|
# However: It shouldn't break much considering plasma 5 is planned to be removed.
|
|
(lib.cmakeBool "KJS_FORCE_DISABLE_PCRE" true)
|
|
];
|
|
}
|