Since the Tooling client in CLI will be a "final" product not
something to be extended i guess its ok that most methods in
ZendL_Tool_Rpc_Endpoint_Abstract are final and there is no way to set
a new loader or something.

But its quite hard to "config" this client currently and there is
probably need to do so anyhow, maybe via plugins that can be loaded
via configuration file or something (see suggestion about config ENV
variable below)

--- In zf-tool@yahoogroups.com, "beberlei84" <beberlei84@...> wrote:
>
> Hello Ralph (and everyone),
>
> i played with the CLI endpoint today and had some problems. Personally
> my include path is a bunch of symlinked libraries. Its way easier to
> change the symlink that to install/deinstall/overwrite libraries all
> the time.
>
> Now it seems the IncludePath Autoloader does not follow symlinks (so
> that for example the OpenId Provider bug is fixed, and i guess no
> loops can occour). But, this way i cannot get any providers or
> manifests into Zend_Tool Registry.
>
> How would one do this? It would probably be great to add an ENVIROMENT
> variable "ZF_CONF_FILE" that points to an Ini file that can have
> optional pathes to search? or is there anything possible in this area
> currently?
>