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

[Jan Rękorajski]

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?

-- 
Jan Rękorajski                    | PLD/Linux
SysAdm | baggins<at>pld-linux.org | http://www.pld-linux.org/