KDE Qt Patch Collection - Tarballs

[A. Wilcox]

On Oct 12, 2022, at 1:15 PM, Neal Gompa <ngompa13 at gmail.com> wrote:
> 
> On Wed, Oct 12, 2022 at 2:12 PM Ben Cooksley <bcooksley at kde.org <mailto:bcooksley at kde.org>> wrote:
>> 
>> On Thu, Oct 13, 2022 at 12:53 AM Neal Gompa <ngompa13 at gmail.com> wrote:
>>> 
>>> On Wed, Oct 12, 2022 at 6:23 AM Ben Cooksley <bcooksley at kde.org> wrote:
>>>> 
>>>> It has come to my attention after noticing abnormal activity on our Gitlab instance this evening that at least one distribution is fetching tarball archives for the KDE Qt Patch Collection directly from Invent.
>>>> 
>>>> This is not a workload that invent.kde.org is intended to support and therefore places abnormal load on the system - especially in the case of QtWebEngine due to it's size. Analysis of the logs indicates that this type of activity is being conducted by both an RPM based distribution, as well as by Alpine Linux (see https://git.alpinelinux.org/aports/tree/community/qt5-qtserialbus/APKBUILD?h=3.16-stable)
>>> 
>>> But I'm going to use this to make a point here: I asked for
>>> tag-releases of the KDE Qt patch set earlier this year because the
>>> current situation is a huge mess[1]. The advice I continue to receive
>>> from KDE developers is to just fetch HEAD and ship that. Aside from
>>> being absolutely nuts to keep track of, you're telling us that the KDE
>>> GitLab instance can't handle it.
>> 
>> 
>> Actual Git clones should be used.
>> 
> 
> Most of us are not going to do that, since our tooling is optimized
> around tarballs. When I say "fetching HEAD" I mean pulling from master
> using the tarball generator URL.


This came up in Adélie.  One of our packagers tried to just copy the Alpine recipe and I stressed that KDE does *not* support this workflow and this would get us in trouble.  (I thought perhaps Alpine had a pass.)

The solution I came up with that we are using is a patch file created by git.  It requires a single git clone each time there is a new KDE patch release, then you just create a patch.  The tooling I wrote names each one `kde-lts.patch` in its respective packaging directory.

I’m not saying this is a great flow, but it is one that is automatable and repeatable.

Best,
-A.

--
A. Wilcox (they/them)
Software Engineer
Wilcox Technologies Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/distributions/attachments/20230205/d72d1d60/attachment.htm>