Path: csiph.com!au2pb.net!feeder.erje.net!us.feeder.erje.net!news.linkpendium.com!news.linkpendium.com!panix!not-for-mail
From: Grant Edwards <invalid@invalid.invalid>
Newsgroups: comp.lang.python
Subject: Re: Automating build from source (was: Automating Sphinx generated documentation)
Date: Fri, 18 Sep 2015 01:54:45 +0000 (UTC)
Organization: PANIX Public Access Internet and UNIX, NYC
Lines: 17
Message-ID: <mtfqt5$j3q$1@reader1.panix.com>
References: <41302A7145AC054FA7A96CFD03835A0A0B9D749B@EX10MBX02.EU.NEC.COM> <mailman.15.1442533060.16376.python-list@python.org>
NNTP-Posting-Host: c-24-118-110-103.hsd1.mn.comcast.net
X-Trace: reader1.panix.com 1442541285 19578 24.118.110.103 (18 Sep 2015 01:54:45 GMT)
X-Complaints-To: abuse@panix.com
NNTP-Posting-Date: Fri, 18 Sep 2015 01:54:45 +0000 (UTC)
User-Agent: slrn/1.0.2 (Linux)
Xref: csiph.com comp.lang.python:96790

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