[chora] Problem setting up Chora (solved)

[Chuck Hagenbuch]

Quoting Graeme Merrall <graeme at inetix.com.au>:

> Found the problem. It was the @include buried in importConfig in the
> horde libs which didn't show up because of the @. I noticed that some
> classes check that a file exists but others don't. Is there a plan to
> make this more consistent?

Not a detailed plan, but ideally, we'd definitely like to do this. What do folks
think of $registry->pushApp() taking an option to die on errors?

-chuck

--
Charles Hagenbuch, <chuck at horde.org>
The alligators were there, too, in a bathtub inside the house.