Packaging LTS versions of software

[Aleix Pol]

On Thu, Oct 15, 2020 at 2:02 AM Aleix Pol <aleixpol at kde.org> wrote:
>
> On Mon, Aug 10, 2020 at 1:50 PM Alexander Larsson <alexl at redhat.com> wrote:
> >
> > On Sun, Aug 9, 2020 at 10:40 PM Aleix Pol <aleixpol at kde.org> wrote:
> > >
> > > Dear flatpakers,
> > > I keep getting requests [1] to package the LTS version of this
> > > software besides the last stable version of it.
> > >
> > > Does anyone know how that would work?
> >
> > I can't speak to whether this is the right thing to do, but in
> > practice this is possible in two ways. Either you package it with the
> > same app id but a different branchname. I'm not sure how well this
> > works with the flathub builssystem atm. I mean, we do support this for
> > e.g. extensions and runtimes (where you need a custom branch name). I
> > *think* it may work if you store your lts files on a git branch called
> > e.g. "branch/lts", but it would need some testing.
> >
> > Alternatively you can create a separate app id for the lts version and
> > treat it as a completely separate app.
> >
> > Which you choose is up to you, if you use multiple app ids they both
> > get visible as two parallell desktop files, but can't typically see
> > each others files, whereas if you use a branchname only one is active
> > (startable via desktop file) at once.
>
> Hi,
> I decided to give it a go with using the same app id.
> I created such a branch here:
> https://github.com/flathub/org.qgis.qgis/tree/branch/stable
>
> How should I proceed now so flathub takes notice?
>
> (Very belated) Thanks!
> Aleix

And I see that flathub downgraded all the clients to the stable
version. This is a bit weird...

Aleix