https://bugs.kde.org/show_bug.cgi?id=386070
Bug ID: 386070
Summary: KTextEditor should allow overriding builtin scripts on
a system-wide level
Product: frameworks-ktexteditor
Version: unspecified
Platform: Compiled Sources
OS: All
Status: UNCONFIRMED
Severity: wishlist
Priority: NOR
Component: general
Assignee: kwrite-bugs-n...@kde.org
Reporter: rjvber...@gmail.com
Target Milestone: ---
KateScriptManager::collect() says this:
```
// then resources, e.g. the stuff we ship with us
dirs.append(QLatin1String(":/ktexteditor/script/") + type);
// then all other locations, this includes global stuff installed by
other applications
// this will not allow global stuff to overwrite the stuff we ship in
our resources to allow to install a more up-to-date ktexteditor lib locally!
```
While I can understand the reasoning I think the current implementation goes a
bit too far in that it makes it impossible for distributions to ship adapted
versions of the builtin scripts (cf. #385413).
In fact, I even wonder how effectively the intended result is achieved, if at
all. With this prioritisation, no on will be installing modified versions of
builtin scripts anywhere but in the writable GenericDataLocation (most likely
in individual home directories).
AFAICT all this order achieves is to make the non-writable GenericDataLocations
off-limits for scripts that would override the builtin scripts.
IMHO (and unless I'm missing something) the algorithm should be:
- look in all appropriate directories under all GenericDataLocations
- look in the builtin resources
- pick the scripts with the latest revision number only.
--
You are receiving this mail because:
You are watching all bug changes.
