On Fri, Feb 22, 2013 at 3:41 AM, Evan Nemerson <[email protected]> wrote:
> I've created a repository on GitHub ("vala-extra-vapis" [1]) to house
> our external VAPIs.
>
> This repository has a very low barrier for entry. Unlike the bindings
> distributed with valac, I don't plan to provide much review or
> oversight. Basically, the only requirement for getting bindings into
> the repository is an open source license (preferable MIT or a similarly
> permissive license).
>
> vala-extra-vapis is designed to be used as a git submodule, and it will
> only contain *.vapi and *.deps files (as well as the README). All
> tests, examples, documentation, and other supplemental information will
> go in a second repository, "vala-extra-vapis-supplemental" [2] (yes, I'm
> aware the name seems both repetitive and redundant). I'm still working
> on getting the infrastructure in place to automatically run the tests
> and generate documentation, but that should happen soon.
>
> If you have created bindings for libraries which are not being
> distributed with the library they bind (or with valac), I hope you'll
> consider submitting them for inclusion in vala-extra-vapis through the
> issue tracker on GitHub.
>
> Just to be clear, I still prefer that bindings be distributed with the
> library they bind when possible (see [3]). However, I hope this will
> provide an easier alternative to trying to get them distributed with
> valac.
>
Evan,
That's a great idea! What do you think about opening up this repo for
metadata files as well?
I ask because we're using WebKitGTK via the GIR binding, but it requires a
number of fixes in the metadata file to work correctly. It would be great
if we could share these changes with other projects.
- Eric
_______________________________________________
vala-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/vala-list