On Tue, Sep 7, 2021 at 8:48 PM Vlad Zahorodnii <vlad.zahorod...@kde.org> wrote:
> On 9/5/21 3:18 PM, David Faure wrote: > > On dimanche 5 septembre 2021 12:26:50 CEST Ben Cooksley wrote: > >> On Sun, Sep 5, 2021 at 10:22 PM David Faure <fa...@kde.org> wrote: > >>> For frameworks, I think we should be able to write a one-time script > that > >>> generates .kde-ci.yml files using the dependencies listed in kde-build- > >>> metadata (and the platforms listed in metainfo.yaml) ? > >> > >> Yes, that should work nicely (although that information now lives in > >> sysadmin/repo-metadata, dependencies folder) > > > > All done for Frameworks. > > > > The script that collects platforms from metainfo.yaml won't be useful for > > other KDE modules, but the script that collects deps from > dependency-data-kf5- > > qt5 is attached, in case it's useful to anyone else. > > Is there a file that maps legacy project paths to gitlab project paths? > dependency-data-kf5-qt5 lists projects with their legacy paths. > The individual project YAML files in sysadmin/repo-metadata contain this information. The legacy project path can be found under 'projectpath' while the Gitlab paths are under 'repopath' > vlad > Cheers, Ben > >> Once we've transitioned across to the .kde-ci.yml files the existing > >> dependency metadata and branch group files will no longer be required. > >> (We'll need to work out a way of exporting this information for easy > >> consumption by kdesrc-build and other clients before it can be removed > >> though) > > > > OK. Duplication is bad so I agree :) > > > >
