[dev] using some backported horde 2.x functionality in IMP 3.x

[Chuck Hagenbuch]

I need an opinion on development practice here:

If I need to backport some functionality from IMP HEAD to IMP RELENG_3, and
it has to rely on code that was not in Horde 2.0, do I _have_ to bundle
those libraries into IMP 3.x? Or would it be acceptable if the feature was
controlled by a configuration setting, so that the code _could_ run with
Horde 2.0, but would require a later release (2.2, I guess) if you wanted to
turn the feature on?

-chuck

--
Charles Hagenbuch, <chuck@horde.org>
"People ask me all the time what it will be like living without otters."
 - Google, thanks to Harpers