Re: [PATCH] docs: add virtualenv to Documentation's build chain

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 20 Jun 2017 16:51:40 +0200
Markus Heiser <markus.heiser@xxxxxxxxxxx> wrote:

> This add a virtualenv [1] with we can control the versions
> of Documentation's (python) requirements. It also changes the
> default behavior, if sphinx is not installed on the OS.
> 
> If Sphinx is not available make builds a virtualenv under
> Documentation/local and installs the requirements from
> Documentation/sphinx/requirements.txt with pip [2].

I appreciate the work done on this, but I still do not think that going
off and installing external software in response to a kernel make command
is appropriate.  Any software installation must require, at a minimum, an
explicit request from the user first.

It would be nice to have, say, a script that can ensure that a target
system is capable of building the docs.  That would preferably include,
as an option, all the awful LaTeX stuff needed for a PDF build.
Preferably it would provide the option of using the system's package
manager or building a venv - but the latter only works for the sphinx
part, of course, and not LaTeX.

I totally agree with taking the pain out of setting up a build
environment, but automatically going off to pull down software off the
net and running it on some developer's build machine is not going to fly.

Thanks,

jon
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux