Re: So, did anybody subscribe yet?

Tollef Fog Heen said:

> Technically, it's not a problem to include it in the tree, but I'm not

The different structure between distributions is already allowed for by mechanisms built into the Apache source code, so this is not a problem.

There are two purposes in including build files into the tree. The first is to give the end user the option of trying out the latest bleeding edge version without waiting for their vendor to catch up.

The second purpose is to provide a reference install for that particular package style in the hope of limiting the proliferations of package layouts out there. A difference between RPM based systems and Debian based systems makes sense, and is already catered for. But if every Debian derived system has their own layout, we have a mess that would be good to try and avoid.

As a side effect of this, the packaging files that are in tree should not (and currently don't) contain any patches. If a patch is necessary, a change should be made directly to the source code. The RPM spec files for example were based on Redhat RPMS, and have had all the patches removed. The problems the patches were trying to fix have been incorporated into the source tree.

Regards,
Graham

--

Do you need help?

In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related httpd.apache.org Links announce bugs cvs dev docs gui-dev modproxy-dev packagers testers Request more information about Pantek