NEW: graphics/py21-pil-1.1.4

[robert@…]

Port for Python Imaging Library for use with Python 2.1 which is needed for Zope usage.

Homepage: ​http://www.pythonware.com/

Requires: python21 and jpeg

[robert@…]

ATTACHMENT: graphics/py21-pil-1.1.4

[robert@…]

ATTACHMENT: graphics/py21-pil-1.1.4 files

[robert@…]

ATTACHMENT: graphics/py21-pil-1.1.4

[mww@…]

changed this port to work with 'any' python version installed by dports and added docs; ​http://wwwcip.informatik.uni-erlangen.de/~simrweis/dports/py-pil/Portfile

If this is o.k. for you, I'll commit it. If it's not - well.... I'm awaiting your comments;

[mww@…]

as Bill is currently moving from Germany to the U.S., I'll care about this one. Nevertheless awaiting response on comment #4 :)

[rshaw@…]

Well, this is a sticky issue. The reason these py21 versions were created were to ensure they are installed in the python2.1 version (which is the version Zope requires). If I want to have both versions installed (say python2.1 and python2.3), how can I get this PIL installed into both?

I had discussed this at length with Will, but we never came to a final decision on what would work best. One of the ideas was to use variants, but we are unable to reference variants in dependencies.

I would go ahead and commit a py-pil version so at least we can build it into the current python being used in dports. But we still don't have a way to handle forcing this into a specific Python version.

Any ideas?

-rshaw

[mww@…]

the problem with different python verion is, that at least the 'python' binary is afaik overwritten by the last python version installed. To use zope, you'd have to install python21, then install py-pil (or whatever python port you want);

This is not a very nice solution, but I can't think of a better one. We could create variants in every python port... which would be a terrible mess. And you'd have to declare which version you want every time installing a python port.

[rshaw@…]

Markus,

Go ahead and commit the py-pil version you made from this and close this bug. I will be moving ahead to Zope 2.7.0 which uses Python 2.3.2, so I think the best thing to do for all these py-* ports is to change the default python link to the version you want to install them into and proceed like you mentioned in one of your early comments. This is workable until PortSystem 2.0 gets nailed down which I believe will have stuff to handle these types of things.

If you want, I can go ahead and commit your version if you don't have the time.

Thanks, -rshaw

[wbb4@…]

As Robert already pointed out, the reason this was a py21 port was for Zope.

Should we go ahead and commit a py21-pil version and a py-pil version (that will work with any python)? I don't see a solution presenting itself anytime soon (I think with the versioning of dependencies in PortSystem 2, we can do some magic... at least from my discussions with Landon)... I won't have any time at all over the next couple of weeks to deal with this.

I say we commit both, thoughts?

[wbb4@…]

Sorry, I also need to respond to this:

-- the problem with different python verion is, that at least the 'python' binary is afaik overwritten by the last python version installed. To use zope, you'd have to install python21, then install py-pil (or whatever python port you want); --

Zope explicitly uses '${prefix}/bin/python2.1', NOT '${prefix}/bin/python'. So anything that is intended to work with Zope or any Zope products needs to check for python2.1, not just python. The python ports co-exist with each other nicely. I don't even know if the python2.1 port installs a 'python' binary. But that's why it installs both.

-- This is not a very nice solution, but I can't think of a better one. We could create variants in every python port... which would be a terrible mess. And you'd have to declare which version you want every time installing a python port. --

Well, I still say let's go ahead and commit two, py21-pil and py-pil. The versioning/variants and autoconfiguation stuff in PortSystem 2 should help to an extent, but we can't wait until then, I think. (I admit I haven't looked over Landon's draft that he sent... I'm just speaking from discussions I had with him.)

[rshaw@…]

I say we only commit ONE, the generic py-pil case for now. With Zope 2.7 coming out and PortSystem 2.0, I think duplicating the ports or anything else will just make a mess. I'm trying to update the Zope port now (locally) to 2.7.0b3 and test it out with Python 2.3.2. I think for the future, that will be the way to go, and those wanting Python 2.1 with Zope 2.6 series will have to do the appropriate things to install the py-* stuff into Python 2.1.

-rshaw

[mww@…]

commited compromise we (wbb4, rshaw, mww) achieved by mail;