On Sun, Jan 23, 2022 at 6:08 AM Michael Reeves <reeves...@gmail.com> wrote:
> What would be needed to build from a tar ball on Windows. I have a craft > setup locally but it likes to use git. > That is governed by your Craft Blueprint. See https://invent.kde.org/packaging/craft-blueprints-kde/-/blob/master/kde/frameworks/version.ini for an example of how to declare versions that can come from tarballs instead of Git branches/tags. Cheers, Ben > > > Jan 21, 2022 2:10:19 PM Ben Cooksley <bcooks...@kde.org>: > > On Sat, Jan 22, 2022 at 7:52 AM Michael Reeves <reeves...@gmail.com> > wrote: > >> This is being cross posted because I am not subscribed to kde-window and >> replies have not shown up in mail archives when I contacted that list for >> other issues. The bug in question is here: >> >> https://bugs.kde.org/show_bug.cgi?id=442607 >> >> As far as I can see the setup for kdiff3 is correct but does not pull >> translations. >> > > Hi Michael, > > To my understanding Craft does not include explicit support for fetching > translations if you are building directly from the Git repositories. > Instead it relies on the translations being bundled in the > repository/archive it is trying to build. > > For release builds which are done from tarballs this should work fine, > however it does mean nightlies from the Binary Factory will not have > translations included. > > The partial translations you are seeing will be because Craft will be > using release versions of Frameworks - which will therefore have > translations included in them. > > The fix for this is for scripty to synchronise copies of the translations > into our Git repositories - something which will ensure a number of other > translation related items work more smoothly as well. > This is something which I believe is being worked on and tested in a small > handful of repositories currently. > > Cheers, > Ben > >