migrating old metadata (kdesrc-build action needed)
Ben Cooksley
bcooksley at kde.org
Sun Nov 3 20:35:33 GMT 2024
On Mon, 4 Nov 2024, 7:54 am Harald Sitter, <sitter at kde.org> wrote:
> Ahoy
>
Hi all,
>
> Currently we have two sets of duplicated metadata one in the ksb format
> and one in yaml. Nico wants to only have one, and I for one agree with
> this. There are also some broader repo-metadata changes coming, not sure
> how much they impact kdesrc-build but the lack of input from the
> kdesrc-build side is concerning at least. So, someone should get involved
> on those (see the issues/MRs on repo-metadata for details).
>
I can confirm we're looking to make some changes to the general repository
metadata files yes - particularly around removing some keys that don't
quite make sense anymore (like projectpath and repoactive) as needs have
changed and the metadata needs to evolve accordingly.
My previous plan had been to keep them around for compatibility, however
ideally we could drop them - so it would be nice if someone (who steps up
to update kdesrc-build to use the yaml files that serve as configuration
for kde-builder) could also update kdesrc-build to use the new kind /
lifecycle keys for the metadata at the same time.
>
> As for the duplicated metadata it's my understanding kdesrc-build needs to
> be updated to use these:
>
> https://invent.kde.org/sysadmin/repo-metadata/-/tree/master/build-configs?ref_type=heads
>
> Long story short: if nobody steps up and maintains kdesrc-build it will be
> defunct in short order. But not all is lost! kde-builder acts as
> replacement and is on top of the new metadata, so we are technically
> already covered.
>
> HS
>
Thanks,
Ben
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20241104/866d922e/attachment.htm>
More information about the kde-core-devel
mailing list