RKWard | Rework how the (GUI) translations are shipped (!2)

[Thomas Friedrichsmeier]

Thomas Friedrichsmeier commented:


Problem is with the builds based on git, rather than distribution tarballs. This affects the craft builds (Windows / MacOS) and the Launchpad daily builds.
* For craft, we can assume python3, svn, and a network connection, so I guess the most obvious solution will be to include a call to import_translations.py in the craft blueprint.
* For launchpad, none of this is available. So our current solution is based on having a separate repo (https://invent.kde.org/tfry/rkward-po-export) that gets "nested" into the build sources (same as the needed debian-dir). I guess that is still the way to go, but of course the changed layout will have to be mirrored, and the launchpad build "recipes" will have to be updated. No big deal.

--

About copying compile_lang.cmake to each language directory: Could this be handled all inside i18n/CMakeLists.txt, globbing each separate language dir one at a time?

-- 
Reply to this email directly or view it on GitLab: https://invent.kde.org/education/rkward/-/merge_requests/2#note_63691
You're receiving this email because of your account on invent.kde.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/rkward-tracker/attachments/20200621/4c9cd47d/attachment.htm>