I think that all projects must distribute its own VAPI files and install in system's directories defined by vala. This is done by libgda and gxml projects, including its GObject Introspection files, created at build time and installed automatically. Distribution packagers can create different packages for GI and VAPI.
Libgda master have added resently GIR and VAPI files in order to track API updates and unwanted changes. 2012/1/6 Antono Vasiljev <[email protected]>: > On Tue, 2012-01-03 at 16:16 +0200, Denis Kuzmenok wrote: > >> What do you think about making vapi repository like perl's cpan to >> search over different vapi's, and install them easily via commandline >> utils? With storage containing them, of course. > > vapi is not usable without headers and libs. and if this tool will > install headers and libs we are reinventing package manager :) > > _______________________________________________ > vala-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/vala-list -- 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) _______________________________________________ vala-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/vala-list
