-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >>> 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?
No, enabling those without any database backends is pointless. >>> 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… Perhaps, but isn't that how it is done for many other packages that have plugins like that (e.g. libqt4[-sql-mysql|-sql-sqlite], php5[-mysql|-sqlite], postfix[-mysql|-pgsql]). Regards, Tobias -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAlJTxmUACgkQR2BKbzEc4IW4WgCgrcvwIOMBLLXwU+yF0YYa3p15 /DYAn3X84BHVrQHKlRC50Ockoz+HBngN =xlZ0 -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
