#38379: New port "databases/sysbench" ----------------------------------+-------------------------------- Reporter: alexander.janssen@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: haspatch Port: sysbench | ----------------------------------+-------------------------------- Comment (by larryv@…): Replying to [comment:8 alexander.janssen@…]:
Replying to [comment:7 egall@…]:
mysql4 is old and obsolete anyway (I couldn't get it to build on Lion), so you could also just leave out the +mysql4 variant instead
I only included it for completeness. I think it just should be fixed in the mysql4 port, but I don't see a point to fix the client libs just to make sysbench work. What do you suggest? Should I remove it and include it later when the mysql4 port builds again? (should check if there's already a ticket opened for mysql4 not building)
Despite what I said before about conflicting variants, both `mysql4` and `mysql5` are obsolete; do not create variants for either of them. If it’s plausible that users might want to build SysBench without MySQL support, add a `mysql55` variant and declare a dependency on the `mysql55` port. You can set it as a default variant if you want (`default_variants +mysql55`). If you want to support MySQL 5.1 too, add a `mysql51` variant.
The mysql5 port links itself against openssl by default, mysql55 doesn't. Mysql55 has the `+openssl` variant. So I think I'll include the openssl dependency for mysql5 only.
Do not declare dependencies on ports that are not actually used by SysBench. Dependencies of dependencies are handled automatically. -- Ticket URL: <https://trac.macports.org/ticket/38379#comment:12> MacPorts <http://www.macports.org/> Ports system for OS X