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 682202 - VAPIGEN_CHECK in vapigen.m4 always uses the unversioned vapigen.pc file when the second parameter is not specified
VAPIGEN_CHECK in vapigen.m4 always uses the unversioned vapigen.pc file when ...
Status: RESOLVED OBSOLETE
Product: vala
Classification: Core
Component: general
0.17.x
Other Linux
: Normal normal
: ---
Assigned To: Vala maintainers
Vala maintainers
Depends on:
Blocks:
 
 
Reported: 2012-08-19 18:58 UTC by Alexandre Rostovtsev
Modified: 2018-05-22 14:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Alexandre Rostovtsev 2012-08-19 18:58:11 UTC 
In Gentoo, we only provide versioned vala executables and pkgconfig files. That means we have /usr/bin/vapigen-0.14, /usr/bin/vapigen-0.16, /usr/share/pkgconfig/vapigen-0.16.pc, /usr/share/pkgconfig/vapigen-0.18.pc etc.; and we don't have any sort of unversioned "vapigen.pc" or "/usr/bin/vapigen" symlinks.

This makes it very inconvenient to use the standard VAPIGEN_CHECK macro from vapigen.m4, because if VAPIGEN_CHECK is called with an empty second parameter (which is what virtually all users of vapigen.m4 do), then VAPIGEN_CHECK assumes that vapigen.pc exists. And if we patch a package's configure.ac to set the second parameter to VAPIGEN_CHECK, then VAPIGEN_CHECK always sets VAPIGEN_VAPIDIR to the *versioned* vapidir, which typically we do not want.

I recommend that vapigen.m4 check for the value of the VAPIGEN environment variable. If VAPIGEN points to a vapigen executable, the VAPIGEN_CHECK macro should use that version of vapigen instead of searching for the vapigen.pc file which is not be available in some distros.
Comment 1 Jürg Billeter 2012-08-20 09:02:24 UTC 
(In reply to comment #0)
> I recommend that vapigen.m4 check for the value of the VAPIGEN environment
> variable. If VAPIGEN points to a vapigen executable, the VAPIGEN_CHECK macro
> should use that version of vapigen instead of searching for the vapigen.pc file
> which is not be available in some distros.

Yes, it sounds sensible to respect the VAPIGEN environment variable.

That said, I recommend providing one Vala release with unversioned names - presumably the latest stable upstream release. Not necessarily for distro packages but to allow developers to use Vala without having to specify a particular version/branch.
Comment 2 GNOME Infrastructure Team 2018-05-22 14:28:23 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/vala/issues/314.