<div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Sep 7, 2021 at 10:28 PM Vlad Zahorodnii <<a href="mailto:vlad.zahorodnii@kde.org">vlad.zahorodnii@kde.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 9/7/21 1:21 PM, Ben Cooksley wrote:<br>
> On Tue, Sep 7, 2021 at 10:14 PM Vlad Zahorodnii <<a href="mailto:vlad.zahorodnii@kde.org" target="_blank">vlad.zahorodnii@kde.org</a> <br>
> <mailto:<a href="mailto:vlad.zahorodnii@kde.org" target="_blank">vlad.zahorodnii@kde.org</a>>> wrote:<br>
> <br>
> On 9/7/21 12:22 PM, Ben Cooksley wrote:<br>
> > On Tue, Sep 7, 2021 at 8:48 PM Vlad Zahorodnii<br>
> <<a href="mailto:vlad.zahorodnii@kde.org" target="_blank">vlad.zahorodnii@kde.org</a> <mailto:<a href="mailto:vlad.zahorodnii@kde.org" target="_blank">vlad.zahorodnii@kde.org</a>><br>
> > <mailto:<a href="mailto:vlad.zahorodnii@kde.org" target="_blank">vlad.zahorodnii@kde.org</a><br>
> <mailto:<a href="mailto:vlad.zahorodnii@kde.org" target="_blank">vlad.zahorodnii@kde.org</a>>>> wrote:<br>
> ><br>
> > On 9/5/21 3:18 PM, David Faure wrote:<br>
> > > On dimanche 5 septembre 2021 12:26:50 CEST Ben Cooksley wrote:<br>
> > >> On Sun, Sep 5, 2021 at 10:22 PM David Faure<br>
> <<a href="mailto:faure@kde.org" target="_blank">faure@kde.org</a> <mailto:<a href="mailto:faure@kde.org" target="_blank">faure@kde.org</a>><br>
> > <mailto:<a href="mailto:faure@kde.org" target="_blank">faure@kde.org</a> <mailto:<a href="mailto:faure@kde.org" target="_blank">faure@kde.org</a>>>> wrote:<br>
> > >>> For frameworks, I think we should be able to write a<br>
> one-time<br>
> > script that<br>
> > >>> generates .kde-ci.yml files using the dependencies listed in<br>
> > kde-build-<br>
> > >>> metadata (and the platforms listed in metainfo.yaml) ?<br>
> > >><br>
> > >> Yes, that should work nicely (although that information<br>
> now lives in<br>
> > >> sysadmin/repo-metadata, dependencies folder)<br>
> > ><br>
> > > All done for Frameworks.<br>
> > ><br>
> > > The script that collects platforms from metainfo.yaml won't be<br>
> > useful for<br>
> > > other KDE modules, but the script that collects deps from<br>
> > dependency-data-kf5-<br>
> > > qt5 is attached, in case it's useful to anyone else.<br>
> ><br>
> > Is there a file that maps legacy project paths to gitlab<br>
> project paths?<br>
> > dependency-data-kf5-qt5 lists projects with their legacy paths.<br>
> ><br>
> ><br>
> > The individual project YAML files in sysadmin/repo-metadata<br>
> contain this<br>
> > information.<br>
> > The legacy project path can be found under 'projectpath' while the<br>
> > Gitlab paths are under 'repopath'<br>
> <br>
> Thanks! I've attached a quick and dirty python script that parses<br>
> project dependencies from repo-metadata and prints corresponding gitlab<br>
> project paths.<br>
> <br>
> Example usage<br>
> <br>
> python project-deps.py --repo-metadata<br>
> /data/projects/src/repo-metadata/ kde/workspace/kwin<br>
> <br>
> Output<br>
> <br>
> Dependencies:<br>
> 'requires':<br>
> 'frameworks/extra-cmake-modules': '@stable'<br>
> 'plasma/kdecoration': '@stable'<br>
> 'plasma/kscreenlocker': '@stable'<br>
> 'plasma/kwayland-integration': '@stable'<br>
> 'plasma/breeze': '@stable'<br>
> 'plasma/kwayland-server': '@stable'<br>
> <br>
> <br>
> Please note that the above is missing a 'on' section as required for <br>
> each Dependencies section in the .kde-ci.yml file.<br>
Yeah... Is there a database or something that can be queried to fill in <br>
the "on" section?<br></blockquote><div><br></div><div>I'm afraid this is information we have not really collected elsewhere at this time.</div><div><br></div><div>Valid values are: Linux, FreeBSD, Windows, macOS, Android</div><div>(capitalisation sensitive)<br></div><div><br></div><div>Cheers,</div><div>Ben<br></div></div></div>