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 661046 - libgda vapi automatically generated at build time
libgda vapi automatically generated at build time
Status: RESOLVED FIXED
Product: vala
Classification: Core
Component: Bindings
0.14.x
Other Linux
: Normal normal
: ---
Assigned To: Vala maintainers
Vala maintainers
Depends on:
Blocks:
 
 
Reported: 2011-10-06 03:32 UTC by Daniel Espinosa
Modified: 2012-06-25 02:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
VAPI file generated at build time, using updated annotations and GIR file (93.50 KB, text/x-vala)
2011-10-06 03:32 UTC, Daniel Espinosa
Details

Description Daniel Espinosa 2011-10-06 03:32:22 UTC
Created attachment 198398 [details]
VAPI file generated at build time, using updated annotations and GIR file

Master branch and resent commits to LIBGDA_4.2 branch has gained VAPI generation at build time.

Future improvements of libgda 5.x and 4.2.10 will generated its VAPI and install on Vala's vapi directory.
Comment 1 Evan Nemerson 2012-01-14 07:58:44 UTC
This binding is generated already in Vala's repo, so I don't want to just overwrite the vapi we have with this since it will get clobbered if we want to regenerate it.

I think the right solution here is to just remove the bindings from Vala per bug #667907, but if you would prefer to instead provide a patch which modifies the data used to generate the vapi (the stuff in vapi/packages/libgda-4.0) I would be willing to push that.
Comment 2 Evan Nemerson 2012-06-25 02:55:54 UTC
libgda is now installing to the correct location, Vala has been modified to give priority to the unversioned vapi directory, and the libgda vapis distributed with Vala have been marked as being deprecated in favor of those distributed upstream.