subsequent rebuilds of notmuch always re-build sphinx and ruby
david at tethera.net
Mon Apr 22 17:03:05 PDT 2019
Daniel Kahn Gillmor <dkg at fifthhorseman.net> writes:
> On Sun 2019-04-21 16:29:02 -0300, David Bremner wrote:
>> the html rebuild is much faster than the texinfo + info rebuilds.
> agreed, in the runs that i've been doing as well. I was concerned that
> the html rebuild itself may have been *triggering* the rebuild of the
> texinfo stuff, though. Sounds like you don't think that's the case.
>> I've posted some patches for the sphinx-doc issues a couple of hours ago
>> (id:20190421171245.19729-1-david at tethera.net).
> thanks! your own commentary on that series seems to acknowledge that
> there are problems with it (though i don't understand the tradeoffs
There was a problem with the first patch, which I replaced with two more.
> Is there no way to give make itself full visibility into the specific
> generated files so it can do its comparisons directly? I'm obviously
> not asking you to rewrite the entire native sphinx build system, i'm
> just observing that at present it seems suboptimal, though i don't know
> how to fix it either :/
I'm open to ideas, but keep in mind we want to support parallel make,
which means we have to be careful not to trigger multiple invocations of
sphinx-build in parallel.
More information about the notmuch