Requiring a plugin's presence

[James Westby]

On Wed, 2008-03-12 at 13:42 +0200, Ville M. Vainio wrote:
> On Wed, Mar 12, 2008 at 6:15 AM, James Westby <jw+debian at jameswestby.net> wrote:
> 
> >  Currently there is no way to ensure that a plugin is present at
> >  any time, for either a user or a branch. This means that mistakes like
> >  those above are possible.
> >
> >  Would it be worth adding some configuration such that a user can specify
> >  that a certain plugin must be loaded for certain operations? I don't
> >  know how fine grained this should be, but there may be a need there.
> 
> Good thinking. That way, projects can enforce conventions without
> explicitly telling them to every new developer that wants to
> contribute. It's almost as good as adding the "restricting" plugins to
> core.
> 

Well, it's actually possible to remove a core plugin without breaking
the distribution, so even having it in the core doesn't ensure
its presence, it just makes it much more likely.

Thanks,

James