Sorry for the delayed answer. Andrew McMillan wrote: > I guess I'd also be happy for someone else to take over Debian packagin= g > of AWL & DAViCal, so I can concentrate on being upstream for them :-)
I'm currently not actively using DAVical, but I could take over maintenance of both packages if you want. > I don't like the fact that if libawl-php added it's directory into the > PHP search path that then DAViCal would be searching the normal PHP > search path, since it only depends on AWL, and not on any other > libraries that wouldn't be ideal either. I'm not sure I understand your argument, but it seems like it hardly makes a difference. PHP would simply match in the second step of the search (system dir), instead of the first (local dir). The performance impact of this is so minimal I doubt it could be even measured (but if you want I could try it out to be sure). > I guess my preference would be that on installation DAViCal actually > constructed an Apache stanza in answer to some configuration questions,= > and that stanza would of course set the PHP include path in the manner > currently recommended by the installation instructions. What exactly would this question be? To be honest, this all seems like an awful lot of hoop-jumping to accomplish something otherwise very simple: if AWL could ever be used by something other than DAVical, then it should (or rather must) be installed in the normal PHP include dir, if not, it could simply be packaged along inside DAVical. Or am I missing something? Cheers --=20 Leo "costela" Antunes [insert a witty retort here]
signature.asc
Description: OpenPGP digital signature
