We have a package ( dev-perl/DBD-mysql ) which supports SSL for client connections, but depends on virtual/mysql because it also supports being built with embedding. https://metacpan.org/source/MICHIELB/DBD-mysql-4.036/dbdimp.c#L1886-1935 The short of it though is that we need a toggle on it that turns on/off SSL support, and having SSL support on our package needs SSL support on whatever the underlying mechanic is. All current backends of virtual/mysql have SSL as an option in some regards, so it makes sense to expose that via a USE flag. --- =dev-db/mariadb-10.2*[embedded?,server,static?] =dev-db/mariadb-10.1*[embedded?,server,static?] =dev-db/mariadb-10.0*[embedded?,server,static?] =dev-db/mysql-${PV}*[embedded?,server,static?] =dev-db/percona-server-${PV}*[embedded?,server,static?] =dev-db/mariadb-galera-10.0*[embedded?,server,static?] =dev-db/mysql-cluster-7.3*[embedded?,server,static?] ---- mariadb: ssl ( openssl, libressl, yassl ) mysql: ssl ( openssl, libressl, yassl ) percona-server: openssl, libressl, yassl mariadb-galera: openssl, libressl, yassl mysql-cluster: ssl ( openssl, libressl, yassl ) I'd imagine percona and mariadb-galera are the more annoying of the two for not having a simpler USE=ssl to rely on.
I think there is a misunderstanding here. For all stable virtual/mysql providers, some form of ssl is required. The USE flags simply allow choosing the flavor. Only the versions <5.6 have the old ssl USE which allows disabling it. If you really need the use change here on ~virtual/mysql-5.5, I can see your point. However these only exists as unstable portability builds for those migrating or unable to upgrade.
FWIW, the deps on dev-perl/DBD-mysql are incorrect.. it should be RDEPEND="... virtual/libmysqlclient:= embedded? ( virtual/mysql[embedded] )" I may need to add an ssl USE on virtual/libmysqlclient to ensure all providers have it enabled
(In reply to Brian Evans from comment #1) > I think there is a misunderstanding here. > > For all stable virtual/mysql providers, some form of ssl is required. The > USE flags simply allow choosing the flavor. Ah, I made the mistake of relying on eix's output, which shows flag sets for older mysql versions, and in the cases I saw. > I may need to add an ssl USE on virtual/libmysqlclient to ensure all providers have it enabled I'm guessing this is because it *is* optional for mysql-connector-c?
Given the reorganization of mysql stuff this is probably obsolete now.
