Macports Portfile

[Mark Nottingham]

FYI, I've submitted a port file to Macports -
    https://trac.macports.org/ticket/33153

Cheers,

[Olivier Tilloy (osomon)]

Nice, thanks Mark!

It doesn’t look like launchpad knows how to synchronize the bug status with that of the bug you filed on trac.macports.org.
Can I ask you to change the status of this bug once your port is accepted? Thanks!

[Mark Nottingham (mnot)]

Will do.

Two issues have cropped up:

- scons install seems to re-compile a good portion of the library; not sure why. I can work around this, however.

- the version of python to install into is hard-wired to that that scons uses, by this:

    python_lib_path = get_python_lib(plat_specific=True)

In macports, scons is hard-wired to use a particular version of Python, so I can't install pyexiv to Python 2.6 if (for example) scons is installed with Python 2.7.

Having multiple versions of Python on a system isn't that uncommon, so I'm going to make it Python 2.7-only for now, I think. I'm not too familiar with scons; is it possible to allow specifying which version of Python to build with/install to?

Thanks,

[Olivier Tilloy (osomon)]

Sorry for the super late reply…

> In macports, scons is hard-wired to use a particular version of Python,
> so I can't install pyexiv to Python 2.6 if (for example) scons is installed
> with Python 2.7.

I’m not familiar with macports, but can’t you force scons to run with a given version by just running:

    /usr/bin/python2.6 /usr/bin/scons

or

    /usr/bin/python2.7 /usr/bin/scons

I just tested on my Ubuntu box with a sample SConstruct file containing this:

    import sys
    print sys.version

and it behaves as expected (prints 2.6 in the first case, 2.7 in the second case).
Of course this is not on MacOS and not using scons from macports, so results may vary, but not being able to do that would be a shame.

> I'm not too familiar with scons; is it possible to allow specifying
> which version of Python to build with/install to?

It should be, using the technique I described above. This is what is used by the debian/ubuntu packages to build pyexiv2 for 2.6 and 2.7 in the same package.

[Mark Nottingham (mnot)]

I got disappointed with macports (after using it for a few years it was fine, but when I actually tried to upstream things, I wasn't impressed with the response) and have switched to Homebrew.

So, if someone else wants to pick that up, feel free.

In homebrew, btw, there is no management of python packages, so it needs to be packaged using pip / easy_install / etc. Any chance of that happening?

[Olivier Tilloy (osomon)]

> So, if someone else wants to pick that up, feel free.

Thanks for the update Mark. Let’s keep the bug report open and unassign it.

> In homebrew, btw, there is no management of python packages, so it needs to
> be packaged using pip / easy_install / etc. Any chance of that happening?

Interestingly, Adam submitted a merge request a few days ago that implements this!
See https://code.launchpad.net/~adam.russell/pyexiv2/pyexiv2-0.3/+merge/96040.
Your comments, if you are familiar with pip/easy_install, are more than welcome.