-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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). > 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. Keeping those dependencies from build-dep might be tricky though. Or wouldn't that require a separate source package? Regards, Tobias [1] http://wiki.strongswan.org/projects/strongswan/wiki/SQL [2] http://wiki.strongswan.org/projects/strongswan/wiki/AttrSQL -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAlJSeuoACgkQR2BKbzEc4IXRpgCgm60kHST1sC2ougNc81iygG2n 0FwAn2Qz6Dxbkkp5QqOSbZe9R63vGmKa =FiCX -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
