Re: 3.25.90 will probably be delayed

Can you attach your two versions of the .vapi? On Ubuntu 17.10 they are almost identical and would compile against either one. On Thu, 10 Aug 2017 at 10:06 wrote: > On Tue, Aug 8, 2017 at 10:45 PM, mcatanz...@gnome.org wrote: > > OK, I'm done sending emails. If you don't

Re: 3.25.90 will probably be delayed

On Tue, Aug 8, 2017 at 10:45 PM, mcatanz...@gnome.org wrote: OK, I'm done sending emails. If you don't have a mail from me, then your module is probably fine. Michael Another update. Thanks to lots of help from lots of people, I'm down to just three known build failures. (There might be

Re: developer.gnome.org and meson

On Wed, Aug 09, 2017 at 09:03:36PM +0100, Emmanuele Bassi wrote: > > (and it would be painfully slow, it takes several > > hours on my machine to generate the GTK+ docs). > > Distributions typically use something slightly more beefy than a > typical PC hardware for their builds. They have also

Re: developer.gnome.org and meson

On Thu, Aug 10, 2017 at 1:27 AM, Sébastien Wilmet wrote: > On Wed, Aug 09, 2017 at 03:20:38PM +0100, Emmanuele Bassi wrote: >> After all, Linux >> distributions rebuild the documentation when building the binary >> packages anyway > > I see that in the gspell-doc package on

Re: developer.gnome.org and meson and devhelp

On Wed, Aug 09, 2017 at 08:33:09AM -0500, mcatanz...@gnome.org wrote: > developer.gnome.org is going to have some problems because for meson modules > 'ninja dist' does not include generated gtk-doc files in the tarball. At > least one maintainer is working around this by manually generating

Re: developer.gnome.org and meson

On 9 August 2017 at 20:57, Sébastien Wilmet wrote: > On Wed, Aug 09, 2017 at 03:20:38PM +0100, Emmanuele Bassi wrote: >> After all, Linux >> distributions rebuild the documentation when building the binary >> packages anyway > > I see that in the gspell-doc package on Fedora

Re: developer.gnome.org and meson

On Wed, Aug 09, 2017 at 03:20:38PM +0100, Emmanuele Bassi wrote: > After all, Linux > distributions rebuild the documentation when building the binary > packages anyway I see that in the gspell-doc package on Fedora 26, some html pages have links to /home/seb/jhbuild/... (a problem with the

Re: developer.gnome.org and meson

I would prefer if building from git is the same as building from a dist tarball, which means I wouldn't ship any pre-generated files in the tarballs unless it's absolutely necessary. I don't consider the additional dependencies for building the docs an issue, at least for distro builds it isn't. I

Re: developer.gnome.org and meson

In the medium-to-long term, I'd really appreciate if developer.gnome.org stopped trying to extract documentation from random locations inside tarballs, munge the cross-references, and published the HTML on a static website. This would avoid having to generate documentation at all, except when

Re: developer.gnome.org and meson

On Wed, 2017-08-09 at 08:33 -0500, mcatanz...@gnome.org wrote: > Hi, > > developer.gnome.org is going to have some problems because for meson > modules 'ninja dist' does not include generated gtk-doc files in the > tarball. At least one maintainer is working around this by manually >

Re: developer.gnome.org and meson

mcatanz...@gnome.org wrote: > developer.gnome.org is going to have some problems because for meson modules > 'ninja dist' does not include generated gtk-doc files in the tarball. At > least one maintainer is working around this by manually generating tarballs > with gtk-doc included instead of

developer.gnome.org and meson

Hi, developer.gnome.org is going to have some problems because for meson modules 'ninja dist' does not include generated gtk-doc files in the tarball. At least one maintainer is working around this by manually generating tarballs with gtk-doc included instead of using 'ninja dist'. I don't