SPECS: apache1.spec - Provide apache-modname for each module - swa...

[Elan Ruusamäe]

On Monday 21 February 2005 12:50, Radoslaw Zielinski wrote:
> >> ``Provides: %{%{name}_of_another_package}'' in a package with different
> >> functionality is a Bad Thing.  Revision 1.47; you reverted it why?
> >
> > since there are packages that require apache, and can work with apache1
> > and apache2. this is to overcame compile time dependancy.
> >
> > see horde.spec, imp.spec, eventum.spec
>
> This is exactly the reason "P: webserver = apache" was introduced for.
> If you need to depend on mod_foo in any version, "P: apache(mod_foo)"
> should be just the thing.  (Would "webserver(mod_foo)" make any sense...?
> I'm thinking about lighttpd here...)
it doesn't make any sense for lighttpd, as currently there's no way provide 
configuration for lighttpd other than files in %doc

i've created the apache(mod_foo) in apache1.spec
1. should such provides being done for any apache module (i mean external ones 
that have separate .spec files). or just create these on demand (when there's 
need for such dependancy)

2. proceed on with apache.spec? :)

3. horde.spec caused strange dependancy problem for poldek. i think it was 
PreReq: sticking in the dependancy from *previous* version

# poldek --upgrade-
There are more than one package which provide "apache-mod_dir >= 1.3.22":
c) apache-mod_dir-2.0.52-10
d) apache1-mod_dir-1.3.33-2.2
e) apache1-mod_dir-1.3.33-2.4
f) apache1-mod_dir-1.3.33-2.6
g) apache1-mod_dir-1.3.33-3
Which one do you want to install? [a]
error: apache1-mod_dir-1.3.33-3 (cap apache-mod_dir >= 1.3.22) is required by 
horde-3.0.3-2.12

there was available release 2.14 for poldek. removing other package requiring 
similiar new dependancy (eventum) did let poldek upgrade fine. any ideas what 
caused this?

-- 
glen