On lun., 2013-10-07 at 11:12 +0200, Tobias Brunner wrote: > Hi Yves-Alexis, > > > I'm unsure about this, but I'm also unsure what's the difference between > > the sql plugin and the mysql/sqlite plugins. Is the sql plugin without > > at least one of the database backends plugins? > > The sql plugin [1] is a configuration backend based on SQL databases. > The mysql/sqlite plugins are database drivers/interfaces, of which at > least one is required to use the sql plugin (or the attr-sql plugin [2] > for that matter).
My point was: does it make sense to have the sql/attr-sql plugins without any database backend enabled? > > > In any case, I'm not sure about adding the MySQL dependency (both > > build-dep and dep). > > > > At one point, we might create a new -plugins binary package for all > > those extra plugins which might not be needed in the general case but > > that some people might find useful. > > I assume separate packages e.g. libstrongswan-mysql and > libstrongswan-sqlite that provide those backends would make sense. The > sql/attr-sql plugin could still be provided by the default package > without dependencies on any specific SQL implementation/library. Having one package per plugin might be a bit overkill though… > Regards, -- Yves-Alexis
signature.asc
Description: This is a digitally signed message part
