On 10 Apr 2002, Ian Bicking wrote:

> I think it wouldn't even include these -- rather, you'd also include
> what mods were important to your particular project (i.e., Webware would
> have mod_webkit, mod_rewrite, and mod_ssl -- mod_auth_db and mod_ssi
> don't seem important to Webware -- another project might not have
> mod_rewrite, or might have mod_auth_db, etc).

+1, though I might even drop mod_ssl and mod_rewrite on the floor :)
Those can always be "added" by the user when they decide they need them,
at which point they're theoretically more willing to invest some time in
tweaking the config.


> Anyway, this should be clearly directed at *only* Windows.  These issues
> are all much better dealt with by the packaging systems on Linux OSes.

I disagree with this, and I can do so legitimately, as I'm a Linux user
(Mandrake, specifically). In fact, my intention would be to build a
"Webware trivial install" RPM. A savvy Linux user can choose to grab the
RPM (or sources) that will best mesh with everything that's already
installed by the system. On the other hand, someone who may or may not
have already hacked their installed stuff beyond recognition will be able
to grab the "trivial install" RPM and install it so they can get up and
running quickly without screwing up their installed stuff.


> > For future proofing, use Apache 2.0 now, rather than 1.3
>
> I suppose, but it should also be possible to use 1.3 since you aren't
> looking for a featureful server anyway, just a compact and reliable one.

Sure. No reason not to apply the same techniques to both builds. That way,
both 1.3 and 2.0 users can start with a trivial install kit and migrate
Webware into their entire production (whichever Apache it may use) when
they're ready.


> Anyway, this might not be at all difficult, or maybe it's already been
> done.  The whole module system seems to be meant to facilitate this, and
> make Apache easy to trim down.

I'm going to hope that it's not at all difficult :) In fact, I may have
time to build some strawman RPMs later this week. We'll see :)

- t.



_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-devel

Reply via email to