Re: Automating build from source (was: Automating Sphinx generated documentation)

From	Grant Edwards <invalid@invalid.invalid>
Newsgroups	comp.lang.python
Subject	Re: Automating build from source (was: Automating Sphinx generated documentation)
Date	2015-09-18 01:54 +0000
Organization	PANIX Public Access Internet and UNIX, NYC
Message-ID	<mtfqt5$j3q$1@reader1.panix.com> (permalink)
References	<41302A7145AC054FA7A96CFD03835A0A0B9D749B@EX10MBX02.EU.NEC.COM> <mailman.15.1442533060.16376.python-list@python.org>

Show all headers | View raw

On 2015-09-17, Ben Finney <ben+python@benfinney.id.au> wrote:

> The VCS should track only those files that humans edit directly.

While I agree that files automatically generated shouldn't be checked
in to a VCS, I'm in favor of putting key binary files under VCS if
they are required to do the build.  We often check deveopment
toolchains into Subversion.  Subversion handles it just fine, and it
saves having to come up with an entirely different scheme for
archiving toolchain binaries.  [If we build the toolchains ourselves,
we will archive those sources as well.]

--
Grant

Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Automating build from source (was: Automating Sphinx generated documentation) Ben Finney <ben+python@benfinney.id.au> - 2015-09-18 09:37 +1000
  Re: Automating build from source (was: Automating Sphinx generated documentation) Grant Edwards <invalid@invalid.invalid> - 2015-09-18 01:54 +0000

csiph-web