[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-release-team
Subject: Re: Can we get tags and tarballs for the KDE Qt patch collection
From: Ben Cooksley <bcooksley () kde ! org>
Date: 2021-06-08 11:15:21
Message-ID: CA+XidOFG4hgmvaK=ND5H-XVCaek_RFVdCyind27u9TMiwh1=7A () mail ! gmail ! com
[Download RAW message or body]
On Tue, Jun 8, 2021 at 10:52 PM Neal Gompa <ngompa13@gmail.com> wrote:
> On Mon, Jun 7, 2021 at 4:52 PM Albert Astals Cid <aacid@kde.org> wrote:
> >
> > El dilluns, 7 de juny de 2021, a les 20:46:25 (CEST), Nate Graham va
> escriure:
> > > Hello folks,
> > >
> > > The Fedora packagers were mentioning to me today that it would be a l=
ot
> > > easier for them to ship Qt with our patch collection if we made tags
> and
> > > tarballs. Is this something we could look into doing?
> >
> > We explicitly do not want to make releases
> > https://community.kde.org/Qt5PatchCollection#Will_there_be_releases.3=
F
> >
> > Making a release means having to use of a version number, and any
> version number we use will be wrong.
> >
> > Don't think this as a product, think of it as a central place where
> patches are collected.
> >
> > If they want a tarball because using git is a problem, they can always
> use
> https://invent.kde.org/qt/qt/qtbase/-/archive/kde/5.15/qtbase-kde-5.15.ta=
r.bz2
> ?
> >
>
> You *already* are using version numbers and bumped it to 5.15.3:
>
> https://blog.neon.kde.org/2021/06/04/kde-neons-qt-is-now-built-from-kdes-=
git-branches/
>
> This is unreasonable if you're going to make us need fixes from there.
> I'd rather we didn't pretend this is something other than what it is:
> a community maintained uplift of Qt 5.15 while Plasma works to move to
> Qt 6.
>
> Also, that URL is unstable, you'd get different things each time you'd
> fetch from it based on the HEAD of that branch.
>
Gitlab offers stable URLs based on a specific hash if absolutely required,
see:
https://invent.kde.org/qt/qt/qtbase/-/archive/2a2f3cd61f59ccec0eecb09e4a879=
5d7322edfcb/qtbase-2a2f3cd61f59ccec0eecb09e4a8795d7322edfcb.tar.bz2
Please note however that my previous comment on no automated access still
applies.
>
> --
> =E7=9C=9F=E5=AE=9F=E3=81=AF=E3=81=84=E3=81=A4=E3=82=82=E4=B8=80=E3=81=A4=
=EF=BC=81/ Always, there's only one truth!
>
Cheers,
Ben
[Attachment #3 (text/html)]
<div dir="ltr"><div dir="ltr">On Tue, Jun 8, 2021 at 10:52 PM Neal Gompa <<a \
href="mailto:ngompa13@gmail.com">ngompa13@gmail.com</a>> wrote:<br></div><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Mon, Jun 7, 2021 at \
4:52 PM Albert Astals Cid <<a href="mailto:aacid@kde.org" \
target="_blank">aacid@kde.org</a>> wrote:<br> ><br>
> El dilluns, 7 de juny de 2021, a les 20:46:25 (CEST), Nate Graham va \
escriure:<br> > > Hello folks,<br>
> ><br>
> > The Fedora packagers were mentioning to me today that it would be a lot<br>
> > easier for them to ship Qt with our patch collection if we made tags \
and<br> > > tarballs. Is this something we could look into doing?<br>
><br>
> We explicitly do not want to make releases<br>
> <a href="https://community.kde.org/Qt5PatchCollection#Will_there_be_releases.3F" \
rel="noreferrer" target="_blank">https://community.kde.org/Qt5PatchCollection#Will_there_be_releases.3F</a><br>
><br>
> Making a release means having to use of a version number, and any version number \
we use will be wrong.<br> ><br>
> Don't think this as a product, think of it as a central place where patches \
are collected.<br> ><br>
> If they want a tarball because using git is a problem, they can always use <a \
href="https://invent.kde.org/qt/qt/qtbase/-/archive/kde/5.15/qtbase-kde-5.15.tar.bz2" \
rel="noreferrer" target="_blank">https://invent.kde.org/qt/qt/qtbase/-/archive/kde/5.15/qtbase-kde-5.15.tar.bz2</a> \
?<br> ><br>
<br>
You *already* are using version numbers and bumped it to 5.15.3:<br>
<a href="https://blog.neon.kde.org/2021/06/04/kde-neons-qt-is-now-built-from-kdes-git-branches/" \
rel="noreferrer" target="_blank">https://blog.neon.kde.org/2021/06/04/kde-neons-qt-is-now-built-from-kdes-git-branches/</a><br>
<br>
This is unreasonable if you're going to make us need fixes from there.<br>
I'd rather we didn't pretend this is something other than what it is:<br>
a community maintained uplift of Qt 5.15 while Plasma works to move to<br>
Qt 6.<br>
<br>
Also, that URL is unstable, you'd get different things each time you'd<br>
fetch from it based on the HEAD of that \
branch.<br></blockquote><div><br></div><div>Gitlab offers stable URLs based on a \
specific hash if absolutely required, see: <a \
href="https://invent.kde.org/qt/qt/qtbase/-/archive/2a2f3cd61f59ccec0eecb09e4a8795d732 \
2edfcb/qtbase-2a2f3cd61f59ccec0eecb09e4a8795d7322edfcb.tar.bz2">https://invent.kde.org \
/qt/qt/qtbase/-/archive/2a2f3cd61f59ccec0eecb09e4a8795d7322edfcb/qtbase-2a2f3cd61f59ccec0eecb09e4a8795d7322edfcb.tar.bz2</a></div><div><br></div><div>Please \
note however that my previous comment on no automated access still \
applies.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <br>
--<br>
真実はいつも一つ！/ Always, there's only one \
truth!<br></blockquote><div><br></div><div>Cheers,</div><div>Ben </div></div></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic