Re: [PATCH 0/3] Restrict the list of plugins to use

["Juan A. Suarez Romero" <jasuarez igalia com>]

On Thu, 2011-07-28 at 10:30 +0200, Juan A. Suarez Romero wrote:
> And over that refactoring I re-wrote the patch provided by Lionel.
> Now, there
> is a envvar (GRL_PLUGIN_USE) and a parameter (--grl-plugin-use) that
> can be
> used to restrict the plugins to use in the application; therefore,
> application
> will only see the plugins in the list, no matter if there are other
> plugins
> already installed. The only way of loading a plugin not in the list is
> using
> grl_plugin_registry_load() function, that gets the .so itself and load
> it. But
> the other functions (load_directory(), load_all(), load_by_id()) will
> be
> restricted to the list.


Pushed, with some small changes:

- Plugins to use are passed with colons
- Envvar to define the list of plugins to use is GRL_PLUGIN_LIST
- The function in the registry to restrict the list of plugins is
private; so the list of restricted plugins must defined either with the
envvar, or with a parameter to the application.
The reason is that if an application actually wants to restrict the use
of plugins to use, the right way to do is just loading those plugins
that it really needs, using the grl_plugin_registry_load_by_id()
function. So we have less functions to maintain in the API.
In any case, if in future we need to make this function public, we can
make it public.


	J.A.