mod_wsgi 2.3 Portfile

[tomvons@…]

Updated Portfile attached, hard-coded to python2.5. I'm not sure what the proper python version procedure is, but the old one was hard coded to 2.4 so I figure this is an improvement either way.

I also changed the long description to match the modwsgi website.

I added myself to the maintainers line, mostly to be polite. I'm not sure what the proper procedure is here, but feel free to do what you want with that line.

[tomvons@…]

Changed it to nomaintainer, the docs make that sound like the most appropriate thing to do (I don't really want to commit to being the guy, and the old maintainer has clearly moved on).

[macsforever2000@…]

You can be the maintainer with openmaintainer so that anyone can make changes. Did the old maintainer say he wasn't able to be maintainer anymore?

[tomvons@…]

Actually I wasn't so proactive as to ask the old maintainer, mod_wsgi 1.1 was released around 6/07 (with 2.0 coming in 12/07) and it was the most recent in the repo, so I figured the maintainer had moved on. I'll drop an email to be certain, though, and update here if I hear back.

Otherwise I'm fine with the maintainer/openmaintainer setup.

[macsforever2000@…]

Cc Me!

[blb@…]

Attached is an updated patch which updates both files/patch-configure.diff and Portfile to:

• update to 2.4
• add variants for python version
• defaults to python26 if another isn't already selected

[blb@…]

diff to mod_wsgi

[anonymous]

Milestone Port Updates deleted

[blb@…]

See also #20809 for an update to 2.5.

[gtaylor@…]

Cc Me!

[gtaylor@…]

#20809 is safe to steal the hashes from for mod_wsgi 2.5, which is a bugfix release. Are there any potential problems with compiling under the currently active Python interpreter? It seems like this could be funky if you were to upgrade Python versions (perhaps move from 2.x to 3.x).

[blb@…]

Cc reporter of dup #20825.

[jmr@…]

This was updated in r56711.