Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Subject: Re: svn commit: r1793940 - in /httpd/docs-build/trunk: deps.xml
 lib/allmodules.pl
To: dev@httpd.apache.org
References: <20170504235549.701E53A0069@svn01-us-west.apache.org>
 <2f7e7c47-9234-1732-98a0-676a44c48e8c@gmail.com>
 <201705051034.11995@news.perlig.de>
From: Jacob Champion <champion.p@gmail.com>
Message-ID: <fe1fc7c1-9d24-9134-be9d-d64afbf7b941@gmail.com>
Date: Fri, 5 May 2017 09:28:48 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <201705051034.11995@news.perlig.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
archived-at: Fri, 05 May 2017 16:28:54 -0000

On 05/05/2017 01:34 AM, André Malo wrote:
> Well... It was a split-project back then (in CVS even... :-)). I'm also not
> sure we want all those jar files and stuff in the main repo. Most people
> neither use nor need it.

I don't mind having the binaries in a separate place, so much as I mind 
having the text-based stuff there that's tightly coupled to the rest of 
the documentation and code. What we have right now is equivalent to 
putting your project's Makefile into a separate repository and then 
trying to make sure it works correctly for every branch at once.

> Note that once the changes are finalized, you can run `build tools` and upload
> the package to dist/docs

Ah, so there's a dist package for people who can't check out docs-build? 
If we moved some files out of docs-build into httpd, would that affect 
them negatively?

To put it another way: if we were to move all the text files and scripts 
from the docs-build root directory into a docs/manual/build folder in 
httpd, and left the docs-build lib folder that has all the third-party 
dependencies and jars and stuff (so that you still had to sync that down 
from SVN), would there be any downsides compared to today?

--Jacob