On Sun, Nov 23, 2014 at 10:07 AM, Eric Covener <cove...@gmail.com> wrote:
> On Sun, Nov 23, 2014 at 9:53 AM, Victor J. Orlikowski > <victor.j.orlikow...@alumni.duke.edu> wrote: > > To my mind, at least on RPM-based distributions, that sounds like a set > of > > prefixed RPM packages, that install into a non-default system location, > and > > that can be built from APR-Util/APR/httpd source trees. > > > > To be a bit more specific: a buildrpm.sh that takes a templated spec > file, > > does the needed configure and make, and drops out a set of packages that > > would install things under /opt/local. > > > > That about sound about right, Jeff? > Yeah; the existing RPMs for httpd, apr, and apr-util template-ized to be able to install elsewhere and not be part of the system packages is an actual (but partial) solution I was thinking of as a way to make it easy for some class of users. > I'm not sure there's much value in this going forward (as opposed to > say 18 months ago) compared to say the doc or evangelism efforts > advocated in Jeff's other thread. > > * The 2014 releases of RedHat, SLES, and Ubuntu have 2.4. > * There are already options for older RHEL (epel, although it doesn't > seem to be servied & RedHat Software Collections) and older Ubuntu (at > least 1 PPA) > * Users who can't avail of these, or the source itself, are unlikely > to move to some even more unusual way to get httpd > One thing to keep in mind about these is that the level of 2.4 will get older and older and the default configuration differs significantly between them. This doesn't support goals like the following: * actually fix/improve issues in the code and have users able to make use of that on your timeframe, which in turn allows you to provide how-to guides that don't have to pretend that, for example, mod_proxy only works with TCP sockets, since probably none of the distros above have a new enough httpd * providing how-to guides that aren't cluttered up with distro-specific configuration layout --/-- At Sun we had a relocatable distribution of httpd and friends based on something like yum or apt; it was trivial for users to bootstrap and install packages and keep updated, and applicable for use by root and non-root alike. (There was also a system package distribution.) The relocatable distribution was perfect for casual use (really just a couple of minutes to get running) that can evolve into a permanently maintained install. Also, there was no inherent reason why any modern OS couldn't be supported. --/-- If you're doing Python web apps it would be cool to "pip install httpd FRAMEWORK-httpd-wiring" and have a command that wires it up based on framework settings and a bit of other declarative configuration. (similar for other ecosystems with a packaging/build infrastructure) mod_wsgi actually has a version in PyPI that works like this, although it doesn't bring httpd with it. -- Born in Roswell... married an alien... http://emptyhammock.com/
