https://bugs.kde.org/show_bug.cgi?id=510443
--- Comment #2 from Harald Sitter <[email protected]> --- I believe this temporary file is basically just working around the inflexible KConfig API. We'd not need the tmpfile if we could assemble the config in memory. To that end I believe the solution here is to refactor KConfig a bit so it can accept a QIODevice instead of a file path. This would then allow us to create a memfd-backed QIODevice that purely lives in memory and doesn't require the tmpfile dance. Probably needs some restructuring of KConfig internals though so as to not get confused between path-based configs and QIOD-based configs. -- You are receiving this mail because: You are watching all bug changes.
