On Fri, Aug 11, 2017 at 4:10 PM, Stefan Sauer wrote:
> On 08/09/2017 10:11 PM, Nirbheek Chauhan wrote:
> > Somewhat relatedly, the only reason why it takes so long to build docs
> > is because we haven't been improving gtk-doc. There is little
> > technical reason why building our documentation ha
On 08/09/2017 10:11 PM, Nirbheek Chauhan wrote:
> 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
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 sl
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 Fedora 26, some html pa
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 tarbal
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 26, some html pages ha
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 gtkdoc
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
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 neede
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
> generating
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 usi
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 re
12 matches
Mail list logo
