After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 761424 - libgda-5.2.x versions force the usage of older vala-0.26 version
libgda-5.2.x versions force the usage of older vala-0.26 version
Status: RESOLVED FIXED
Product: libgda
Classification: Other
Component: Vala bindings
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Daniel Espinosa
gnome-db Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-02-01 20:40 UTC by Pacho Ramos
Modified: 2016-10-08 08:31 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Pacho Ramos 2016-02-01 20:40:05 UTC
It would be nice if configure could also check for newer versions like 0.30 (the one that is usually supplied with gnome 3.18). It seems that "master" branch already supports 0.30, but I have no idea if any stable release from that branch will be launched in the near future

Thanks
Comment 2 Pacho Ramos 2016-02-06 18:50:32 UTC
Thanks a lot :D

Only a question: is there any reason for being so strict regarding the concrete vala version to be used? I say that because this problem will likely reappear in the future with upcoming vala versions and we needing to update the configure.ac check for supporting that versions :/ Most vala reverse deps are simply forcing a minimum vala version, but not a concrete/fixed one

Best regards
Comment 3 malerba 2016-02-06 18:52:58 UTC
No, there is not, but I don't know how to write the configure script to test for any version of vala, only to test for some specific version... Any idea how to do it?
Regards,
Vivien
Comment 4 Pacho Ramos 2016-02-06 18:59:49 UTC
Most reverse deps (like gnome-tetravex as one random example) are relying on AM_PROG_VALAC macro:
https://www.gnu.org/software/automake/manual/html_node/Vala-Support.html
Comment 5 Daniel Espinosa 2016-02-06 22:53:51 UTC
May we need to relay in valac.m4 I wrote for GXml, check it at

https://git.gnome.org/browse/gxml/tree/m4/valac.m4

As far as I remember some new version of vala may generate a different a API for GDA on  build, but when compiled to new Vala version we need to check if we no break existing applications using VAPI for GDA.

This macro helps on checking API Vala version and makes easy to update to new versions, just use in configure.ac:


VALAC_CHECK([VERSION], [API_VERSION])

If no API version is provided, falls to use your insatalled version.
Comment 6 malerba 2016-02-07 19:58:12 UTC
Hi! I've modified the configure script to use the default version if none is specified, see https://git.gnome.org/browse/libgda/commit/?id=e72c59062f39e89569524f4556cbddb8d00119f4
Comment 7 Pacho Ramos 2016-10-08 08:31:31 UTC
(In reply to malerba from comment #6)
> Hi! I've modified the configure script to use the default version if none is
> specified, see
> https://git.gnome.org/browse/libgda/commit/
> ?id=e72c59062f39e89569524f4556cbddb8d00119f4

I think this last one was forgotten in 5.2 branch, could it be included too? That will fix it in future 5.2.5 version :) 

Thanks!