Issue 823775: use just built python interp. to build the docs. (original) (raw)

Created on 2003-10-14 22:58 by doko, last changed 2022-04-10 16:11 by admin. This issue is now closed.

Messages (5)
msg44777 - (view)	Author: Matthias Klose (doko) *	Date: 2003-10-14 22:58
this patch doesn't change the default behaviour, but does allow passing a PYTHON interpreter for building the docs. Of ycourse you could pass MKHOWTO as well, but then you have to know the environmnet (TEXINPUTS) as well. The "$(shell ...)" construct is already used, so it does not introduce a new incompatibility. [note: I think as the default the just built interpreter should be used to build the docs]
msg44778 - (view)	Author: Martin v. Löwis (loewis) *	Date: 2003-10-18 10:11
Logged In: YES user_id=21627 The patch does not apply to the CVS trunk. Please don't remove the unused MKHOWTO line, and please provide separate patches for 2.3 and the trunk.
msg44779 - (view)	Author: Matthias Klose (doko) *	Date: 2003-11-16 10:23
Logged In: YES user_id=60903 attached is the patch for the trunk. I don't see much sense in keeping the uncommented version, because the new definition tries to cover both cases. Maybe Fred could comment what he likes better.
msg44780 - (view)	Author: Martin v. Löwis (loewis) *	Date: 2004-08-18 12:59
Logged In: YES user_id=21627 As Makefile will always set PYTHON to python atleast, I don't see the point of this patch anymore. I agree the uncommented version could go - anybody who cannot set PYTHON appropriately but still can edit the Makefile might just as well remove $(PYTHON). doko, please update the Makefile as you see fit, and close this patch.
msg44781 - (view)	Author: Matthias Klose (doko) *	Date: 2004-08-18 22:28
Logged In: YES user_id=60903 removed the commented definition of MKHOWTO macro fixed in 1.277 of Doc/Makefile