Hey! I've finally found the problem and solved it. I've added metadata from Vala repository and merged to libsoup's one, and now with attached patch, you can generate VAPI files API equivalent from libsoup source code and the one ditributed with Vala. With this patch, no VAPI break exists between both repositories, with the advantage that VAPI files will be generated automatically for all new API added to libsoup. Please review, compile and make a diff between both VAPI files and if you approve it I could push upstream. 2015-02-12 16:14 GMT-06:00 Zeeshan Ali (Khattak) <zeeshanak gnome org>:
The issue is mentioned in the reverting commit log I provided URL for. Please diff your vapi against vala provided one and coordinate with both maintainers to ensure a smooth transition for all apps. I think we'd want to remove vapi from vala when we add it to libsoup. Thanks for your work on this. On 12 Feb 2015 18:22, "Daniel Espinosa" <esodan gmail com> wrote:Ok. Thanks. I would like to know your issues, in order to take them in account when adding VAPI generation support for this or other projects. 2015-02-12 11:46 GMT-06:00 Zeeshan Ali (Khattak) <zeeshanak gnome org>:Hi Daniel, As much as I love the idea of upstream libraries providing VAPI, I had to revert your patch for now. I looked for some obvious way to fix the issues it caused but I couldn't find any and I got a lot of things to do before the week ends. https://git.gnome.org/browse/libsoup/commit/?id=7fa8478ef8d9e00b30519df149330ce581fb2632 -- Regards, Zeeshan Ali (Khattak) ________________________________________ Befriend GNOME: http://www.gnome.org/friends/-- Trabajar, la mejor arma para tu superación "de grano en grano, se hace la arena" (R) (en trámite, pero para los cuates: LIBRE)
-- Trabajar, la mejor arma para tu superación "de grano en grano, se hace la arena" (R) (en trámite, pero para los cuates: LIBRE)
Attachment:
path-vala-bindings.patch
Description: Text Data