Re: glibmm versions

[p sun fun gmail com]

Thank you, Kjell.

Situation with API/ABI version is really confusing. Is there any rule
you follow when you make a release? Say, new version of glibmm is
issued after new version of glib. 

> From jhbuild moduleset only libgdamm needs glibmm-2.58 (a la master).
Downgrade doesn't work since API for glibmm was changed between 2.4 and
2.56. It looks like only one solution here is to create a local module
set file and build all dependencies around master. 

Thanks.


On Thu, 2018-07-26 at 10:40 +0200, Kjell Ahlstedt wrote:
> glibmm-2.56 was once the tentative ABI-name of a series of new ABI-
> breaking releases of glibmm. Now the still tentative ABI-name is
> glibmm-2.58. It's very confusing. I've tried to explain in a jhbuild
> bug.
> https://bugzilla.gnome.org/show_bug.cgi?id=792047#c6
> https://bugzilla.gnome.org/show_bug.cgi?id=792047#c11
> You shall probably change the requirement in libgdamm to glibmm-2.58
> > = 2.57.1
> Kjell
> On 2018-07-26 07:21, Pavlo Solntsev via gtkmm-list wrote:
> > Hi,
> > Could you please clarify the following. I am trying to compile
> > libgdamm. It requires glibmm-2.56 >= 2.45.31. What does it mean?
> > There
> > is a branch 2.56 which corresponds to glibmm-2.4. How to get
> > glibmm-
> > 2.56? master corresponds to glibmm-2.58. I already filed bug
> > against
> > jhbuild but I am ready to compile glibmm manually. 
> >
> > Thanks.
> >
> >
> >
> > configure: error: Package requirements (glibmm-2.56 >= 2.45.31
> > libgda-
> > 6.0 >= 5.0.2) were not met:
> >
> > No package 'glibmm-2.56' found
>