| Summary: | virtual/mysql needs USE="ssl" | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Kent Fredric (IRC: kent\n) (RETIRED) <kentnl> |
| Component: | Current packages | Assignee: | Gentoo Linux MySQL bugs team <mysql-bugs> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | perl |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Kent Fredric (IRC: kent\n) (RETIRED)
2016-10-02 18:13:46 UTC
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. |