horde-imp requirements

[Elan Ruusamäe]

On Wednesday 21 June 2006 22:08, Paweł Gołaszewski wrote:
> On Wed, 21 Jun 2006, Elan Ruusamäe wrote:
> > > > It seems to me that horde-imp requires mod_authz_host.
> > >
> > > And apache-mod_dir+apache-mod_alias. Ok, I suppose that horde can also
> > > be used with other http servers but those packages were clearly
> > > missing after trying to install horde-imp/apache with poldek. Lack of
> > > the first one caused apache to complain about unknown directives in
> > > config file, lack of the other 2 made it impossible to properly run
> > > horde.
> >
> > the problem is that 'Allow from all' directive is provided by:
> > - mod_auth for apache 1.3 and apache 2.0
> > - mod_authz_host by apache 2.2
> > (- mod_access by lighttpd)
> >
> > and there's no clear way how to require such multiple matched 'virtual'
> > without breaking webserver independency.
>
> Why?
> There is easy way for that.
if it's easy what it would be then. say something. or do it?

> You can simply provide and require httpd(something) feature. It'll solve
> every such problems...
and what would be the pattern making that something?
there are equivalents, but not directly same commands in different webserver. 
what if the directive matches partially?

or just assume that some basic directives are needed to support and implement 
virtuals for:
- access control
 - "Allow from all" (apache>2.2(mod_authz_host), apache<2.2(mod_auth), 
lighttpd(mod_access)
 - "require user foo" (apache<2.2(mod_auth), apache>2.2(mod_authz_(xxx|xxxy)), 
lighttpd(mod_auth))
- directory indexfile (apache(mod_dir), lighttpd(mod_indexfile))

and define them as webserver(a[ccess-]c[ontro]l), webserver(auth[orization]), 
webserver(dir[ectory]index) ?


i'm sorry if i'm not understandable today ;)

> Only problem would be poldek-lotto, but choice_equivalents_manually should
> be turn on by default, IMO.
>
> > in other cases you could add there apache(mod_dir) and
> > apache(mod_alias), which would be provided by apache1-mod_dir or
> > apache-mod_dir, that would preserve independency with apache 1.3 vs
> > apache 2.0 apache2.2, but break for example lighttpd ;) ideas welcome
> > how to solve especially the first case, if any!
>
> lighttpd provides mod_dir-like functionality - I don't see any problems in
> such provides/requires.

-- 
glen