>Number: 2889 >Category: general >Synopsis: Inclusion of RPM spec file in CVS/distributions >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: change-request >Submitter-Id: apache >Arrival-Date: Fri Aug 21 10:30:00 PDT 1998 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: all >Environment: It involves all RPM-compatible platforms (e.g. most Unices) >Description: I prefer to install Apache as an RPM. I downloaded and installed an excellent 1.3.0 RPM, which included all the important modules compiled as DSOs. All you need to do is install the package and comment out the undesired modules from the httpd.conf (and set up the rest etc). Great! I was a happy bunny.
I then came across a couple of modules that rely on v1.3.1, so naturally I look for a 1.3.1 RPM and just do an upgrade. The 1.3.1 RPMs I found didn't contain all the desired modules, and weren't even laid out the same (docs/binaries etc). Next step, then, is to grab the 1.3.0 spec, 1.3.1 source and update the spec file, and build my RPM. Great! I can just picture others around the world having the same dilemma, and going through the same crap. Hence this suggestion. If we have one common spec file to build from, and if we distributed some Apache-endorsed (?) RPMs at release time, much wasted coding time could be avoided. >How-To-Repeat: See http://rufus.w3.org/ for the RPM database. There are various RPMs for Apache, all with different characteristics. >Fix: In order to make Apache easier to install, perhaps a spec file should be adopted and maintained in the source. A small group of volunteers could then build and post some pre-built RPMs for various platforms as part of the release process. I have the basic spec file and configuration patches from the first (best) distribution. I suggest checking them into an /rpm directory in CVS. I still have some improvements in mind that I can make to it. >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]
