Mailing-List: contact packagers-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: packagers@httpd.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <4F43CC5B.5080806@rowe-clan.net>
Date: Tue, 21 Feb 2012 10:54:51 -0600
From: "William A. Rowe Jr." <wrowe@rowe-clan.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: packagers@httpd.apache.org
CC: Michael Felt <mamfelt@gmail.com>
Subject: Re: Binary windows 2.4.x distribution
References: <4F435CCB.4050209@rowe-clan.net> <4F435E8D.8090309@rowe-clan.net>
 <CAN9c_NSt4nh726uBLrpfXNGwMdEas11KGE2imwpPDkUKT0Avtg@mail.gmail.com>
In-Reply-To: 
 <CAN9c_NSt4nh726uBLrpfXNGwMdEas11KGE2imwpPDkUKT0Avtg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

On 2/21/2012 10:40 AM, Michael Felt wrote:
> re: 5, I do not know about conventions on linux distros, and even less on
> windows 7 conventions, but what I am looking to do for AIX is separate the
> required parts )the real rte aka run-time-env with nice to have files such
> as manual and man pages, and maybe other items.
> 
> I would very much appreciate "guidance" regarding how the devs look at the
> different directories, especially what could/should be loaded read-only
> (such as executables and modules and could be md5 signed each individually
> as an additional element of a trusted installation, and files that are
> expected to be edited or modified (such as httpd.conf).

Here is how the various linux distros individually handled this;

  http://wiki.apache.org/httpd/DistrosDefaultLayout

[nothing should need to be edited once you have correctly set up the various
./configure path variables]