[Development] QLibraryInfo::path(): to deprecate or not to deprecate?

[Thiago Macieira]

On Tuesday, 28 July 2026 08:39:48 Pacific Daylight Time Kai Köhne via 
Development wrote:
> Instead, the canonical way to solve this is to merge the Qt translations at
> compile time:
> 
> https://codereview.qt-project.org/c/qt/qtbase/+/756031

Ok, so the canonical way is that there should be a single file to be loaded, 
per domain anyway. The missing bit is finding it among the multiple paths() 
that QLibraryInfo can return.

> So for this _specific_ example, we probably should just fall back to
> QLI::paths().first():
> 
> https://codereview.qt-project.org/c/qt/qtbase/+/756032

Which is what code is currently doing, but may not be correct if the first path 
is not where the content ended up installed.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Principal Engineer - Intel DCG - Platform & Sys. Eng.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5176 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/development/attachments/20260728/1917a9c5/attachment.bin>