#39510: py-oursql @0.9.2 Add variants for mysql --------------------------+------------------------ Reporter: s@… | Owner: habnabit@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: haspatch Port: py-oursql | --------------------------+------------------------ Changes (by jmr@…): * cc: habnabit@… (removed) * owner: macports-tickets@… => habnabit@… Comment: Do you have a specific need for this module under python 2.4 and 2.5? If not, we really shouldn't add any more modules for these python versions, which are EOL and no longer getting security fixes. -- Ticket URL: <https://trac.macports.org/ticket/39510#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X

#39510: py-oursql @0.9.2 Add variants for mysql --------------------------+------------------------ Reporter: s@… | Owner: habnabit@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: haspatch Port: py-oursql | --------------------------+------------------------ Comment (by s@…): Replying to [comment:1 ryandesign@…]:

Then you should also add variants for mysql56, percona and mariadb. There has to be a better way to handle multiple versions of mysql than the n^2^ variant conflicts list. Is there no concept of a group of ports all of which satisfy a given dependency and variants for each are mutually conflicting?

I'd never even heard of percona or mariadb and I didn't realize that there was a mysql56 port since I was looking at the py-mysqldb which has mysql4, mysql5, mysql51, and mysql55. (And frankly, I can't even tell what the difference between mysql5 and mysql51 is. They seem identical except that mysql5 includes openssl and mysql51 requires the +openssl variant.) Although there is only one version of mariadb in MP, it seems that it is trying to be binary compatible with various versions of MySQL so one could easily imagine MP having mariadb51 and mariadb55 so yet more variants one could have. It seems unmaintainable. I also just noticed that there is a newer version of oursql, 0.9.3.1. It seems better to get support for others mysql variants in first and then change version (or the other way around) rather than make both changes at once, but I'm willing to do both at once if that's desired. -- Ticket URL: <https://trac.macports.org/ticket/39510#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X

#39510: py-oursql @0.9.2 Add variants for mysql --------------------------+------------------------ Reporter: s@… | Owner: habnabit@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: haspatch Port: py-oursql | --------------------------+------------------------ Comment (by s@…): The attached [https://trac.macports.org/attachment/ticket/39510/Portfile .py-oursql-1.diff Portfile.py-oursql-1.diff] patch does the following:[[BR]] 1. Update py26-oursql and py27-oursql to version 0.9.3.1;[[BR]] 2. Update py31-oursql, py32-oursql, and py33-oursql to version 0.9.3;[[BR]] 3. Drop mysql4 variant; and[[BR]] 4. Add mariadb and percona variants. mysql4 is dropped because I cannot even build it. I could probably fix the build but mysql4 is ancient and it seems some people want to just [http ://mac-os-forge.2317878.n4.nabble.com/Proposal-Delete-mysql4-td115981.html drop it]. The py3k release of oursql 0.9.3 does not compile for Python 3.3. See [https://bugs.launchpad.net/oursql/+bug/1067767 launchpad] for details. The attached [https://trac.macports.org/attachment/ticket/39510/patch- oursqlx-oursql.c.diff patch-oursqlx-oursql.c.diff] fixes this. The patch has also been sent [https://bugs.launchpad.net/oursql/+bug/1067767/comments/2 upstream]. -- Ticket URL: <https://trac.macports.org/ticket/39510#comment:6> MacPorts <http://www.macports.org/> Ports system for OS X

#39510: py-oursql @0.9.2 Add variants for mysql --------------------------+-------------------------------- Reporter: s@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: haspatch Port: py-oursql | --------------------------+-------------------------------- Changes (by toby@…): * owner: habnabit@… => macports-tickets@… -- Ticket URL: <https://trac.macports.org/ticket/39510#comment:8> MacPorts <http://www.macports.org/> Ports system for OS X

#39510: py-oursql @0.9.2 Add variants for mysql, update to 0.9.3.x --------------------------+---------------------- Reporter: s@… | Owner: larryv@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: py-oursql | --------------------------+---------------------- Changes (by larryv@…): * status: assigned => closed * resolution: => fixed Comment: Updated in r111087:111088. I unrolled your variant loop, so to speak, because I found it rather difficult to figure out what was going on. Until some functionality is implemented in base (something I’ve been thinking about), it’s best to err on the side of clarity in Portfiles, even if it’s a little tedious. -- Ticket URL: <https://trac.macports.org/ticket/39510#comment:10> MacPorts <http://www.macports.org/> Ports system for OS X