Update on Status of Gitlab Migration

Ben Cooksley bcooksley at kde.org
Sun Apr 12 00:06:20 BST 2020


On Sun, Apr 12, 2020 at 11:04 AM Johan Ouwerkerk <jm.ouwerkerk at gmail.com> wrote:
>
> On Sun, Apr 12, 2020 at 12:49 AM Johan Ouwerkerk <jm.ouwerkerk at gmail.com> wrote:
> >
> > Yes the only reason why a cleanup script might be needed is if the
> > logical path used to express the repo in dependency information
> > changes at the same time. E.g. suppose a `frameworks/kf5foo` gets
> > remapped to `frameworks/kf5/foo` or something like that. In that case
> > unless you use the flat repository layout, kdesrc-build would try to
> > clone a new `frameworks/kf5/foo` repo, leaving your old
> > `frameworks/kf5foo` to consume some wasted disk space.
> >
>
> This is obviously a poor example, but the same problem occurs if
> something moves from playground to extragear. Basically if the
> `projectpath` YAML key changes.

I had been considering adding the Gitlab Project ID number to the YAML
metadata files as a way of allowing us to track projects through their
whole lifetime.

>
> Regards,
>
> - Johan

Cheers,
Ben




More information about the kde-core-devel mailing list