[packages/wlroots0.18] rename to wlroots0.18

[Jan Palus]

On 22.02.2025 00:54, Jan Rękorajski wrote:
> On Sat, 22 Feb 2025, Jan Palus wrote:
> 
> > On 21.02.2025 23:55, Jan Rękorajski wrote:
> > > On Thu, 20 Feb 2025, atler wrote:
> > > 
> > > > commit b58dea8d2398b217f33147fa9388e91fc580530c
> > > > Author: Jan Palus <atler at pld-linux.org>
> > > > Date:   Thu Feb 20 13:21:46 2025 +0100
> > > > 
> > > >     rename to wlroots0.18
> > > > 
> > > >  wlroots.spec => wlroots0.18.spec | 2 +-
> > > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > > ---
> > > > diff --git a/wlroots.spec b/wlroots0.18.spec
> > > > similarity index 99%
> > > > rename from wlroots.spec
> > > > rename to wlroots0.18.spec
> > > > index 611d68d..40a38f2 100644
> > > > --- a/wlroots.spec
> > > > +++ b/wlroots0.18.spec
> > > 
> > > But why? There is absolutly no need for this prolifertion.
> > > Especially for one, single, package.
> > 
> > Because wlroots is known for introducing heavy changes with each and
> > every release and downstreams are known to seriously lag behind those
> > changes. cage in particular. wlroots maintainers recognized the problem
> > and renamed files to include major and minor version (libwlroots.so ->
> > libwlroots-0.18.so, wlroots.pc -> wlroots-0.18.pc, /usr/include/wlroots
> > -> /usr/include/wlroots-0.18) so different versions can be installed in
> > parallel without conflicts.
> 
> This makes more sense now. I still don't like it.
> But, in this case I'll leave the choice up to you - either keep the
> versioned package(s) and drop the unversioned one, or stick to one
> unversioned package and update it once downstreams are ready.
> There are just 3 packages depending on it, is it worth to keep a
> different version of the library for each one and evetually have
> orphaned, unused library in system and distro?

As a matter of fact I wanted to do upgrade in wlroots.spec just as you
suggested. I had the changes ready since sway 1.10 was released (late
October) and waited patiently until other compositors catch up. 7 months
after wlroots 0.18.0 was published wayfire still does not have a version
with wlroots 0.18.x support and I'm not really big fan of pulling ~1500L
patch that may work or may not. Situation is still not as dramatic (yet)
as with cage in wlroots 0.16/0.17 days which lacked release for 2 years.

While I'd prefer to have single spec too, I don't think holding back
other compositors which would benefit from new wlroots features is a
good choice only because one of them is slow to adapt. Hence the
decision to follow upstream direction with versioned library, which I
very much welcome, and reflect new naming in our packages too.

What I can offer from my side is to send an email with package removal
request for wlroots versions not being dependency of any other package
as I don't really care for them.

And while currently we have only 3 compositors packaged, this my change
with time making various wlroots versions availability more relevant.
Current list of projects using wlroots is a bit longer:

https://gitlab.freedesktop.org/wlroots/wlroots/-/wikis/Projects-which-use-wlroots