On Tue, May 30, 2017 at 4:10 PM, Luigi Toscano <luigi.tosc...@tiscali.it> wrote: > On Tuesday, 30 May 2017 16:06:56 CEST Harald Sitter wrote: >> Is there a reason ECM's project is placed in kdesupport rather than >> frameworks? >> >> https://cgit.kde.org/sysadmin/repo-metadata.git/tree/projects/kdesupport/ext >> ra-cmake-modules >> >> Seems a bit fishy at best and practically means that if ECM ever were >> to get translations it wouldn't inherit the translation settings >> applying to frameworks/* >> https://cgit.kde.org/sysadmin/repo-metadata.git/tree/config/i18n_defaults.js >> on >> >> Can we fix this or is this actually intentional? > > > I think that we can fix that only if we define a tier 0 for Frameworks. > Otherwise tier 1 frameworks wouldn't be able to depend on it, by definition.
That was actually the reason, as far as I remember. The plan was to move things up to cmake at some point, which never happened because we'd obviously have to require new versions of cmake all the time. Tier 0 works for me, I agree it's what it is anyway, they're even released together. Aleix
