https://bugs.kde.org/show_bug.cgi?id=422529
--- Comment #20 from feat...@engineer.com --- (In reply to Artem S. Tashkinov from comment #19) > (In reply to feature from comment #15) > > > > And for a smooth transition, the load function can be wrapped with a try > > catch clause that would try to load with the prefix, and if it fails look > > for the config outside the prefix and move it inside the prefix, living a > > symbolic link outside. > > If you move the config file inside the prefix, there's no need for a > symlink. No symlinks please, it will only confuse people. I've suggested using symlinks, for the cases in which external programs (not using kconfig) are looking for these config files in a hardcoded way... To make sure nothing breaks. these symlinks would only appear for people who migrate from a previous version, and it's very easy to clean up. Conversely, they are also quite easy to create if needed, and most people would probably not use any such external program... So I don't feel strongly about it either way. I was just addressing the concern that things might break if the config paths are changed, and I think my original suggestion is addressing any corner case that may arise. -- You are receiving this mail because: You are watching all bug changes.
