[PATCH 0 of 7] Build documentation using distutils - v4

[Martin Geisler]

Dan Villiom Podlaski Christiansen <danchr at gmail.com> writes:

> On 4 Dec 2009, at 10:54, Martin Geisler wrote:
>
>> In the second commit I merged patch 3 and 4. I did that because I
>> will much rather use distutils as it's documented to be used (by
>> putting the 'share/' directly into the paths in data_files) instead
>> of importing something from distutil and fixing their bug. The goal
>> is to make it as simple as possible, not necessarily fix all
>> distutils bugs:
>> 
>>  http://hg.intevation.org/mercurial/crew/diff/68964567e406/setup.py
>
> Well, I still disagree, but respect your decision ;)

Thanks.

>> I hope to get the doc-building patch in soon. I'll probably rework it
>> so that it just calls the simple interface from Docutils twice, that
>> is the publish_programmatically (or what's it's called). Again, I
>> really think we should keep it simple when we can.
>
> I'll take a look and see if I can simplify what I have, ok? The core
> problem, here, is that publish_programatically doesn't provide access
> to dependencies.

I agree that it's a shame that we don't get nice automatic dependency
tracking. But it's not a core problem -- it doesn't really matter.
Building the documentation is still quite fast.

We should start by getting something in that matches the current
behavior of the Makefile. We can then look at being fancy later.

-- 
Martin Geisler

VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20091205/7cd10da6/attachment.pgp>