Bugzilla Bug 35279

As mentioned in bug 35278, attached is an ebuild for PythonMagick the Python
module for GraphicsMagick (http://www.procoders.net/moinmoin/PythonMagick).

At the moment this ebuild is hardcoded against GraphicsMagick-1.0.4 and
Boost-1.30.2 because of the requirements for unpacking files in the correct
location and making/installing. Some suggestions on making this more dynamic
would be great!

Although it is possible to just 'emerge pythonmagick' I have then had problems
if the perl module is compiled with USE='perl' emerge graphicsmagick. Running
emerge graphicsmagick again cures this.

Chris

Created an attachment (id=21828) [details]
PythonMagick-0.5.ebuild (New Package) ebuild

I suggest dev-python for this ebuild.

Created an attachment (id=22132) [details]
pythonmagick-0.5 ebuild - second attempt

This version builds outside of the boost tree (i.e. doesn't unpack the boost
source just to compile this one). Also means it doesn't reinstall
/usr/lib/libboost_python*.

Problems with emerge pythonmagick without graphicsmagick being installed now
seem to be solved.

Does need the additional files Jamfile and boost-build.jam (see subsequent
attachments)

Created an attachment (id=22133) [details]
Modified Jamfile from distribution to build outside boost tree

Created an attachment (id=22134) [details]
boost-build.jam to allow build outside boost tree

Building outside the tree depends on boost-1.30.2-r1.ebuild submitted as bug
#35718

Created an attachment (id=27305) [details]
Update for GraphicsMagick-1.05 and Boost-1.31 (Python 2.3)

To build with Boost-1.31 need boost-jam-3.1.9, also attached.

Created an attachment (id=27306) [details]
Modified Jamfile

Created an attachment (id=27307) [details]
Jamrules

Created an attachment (id=27308) [details]
boost-build.jam

Created an attachment (id=27310) [details]
boost-jam-3.1.9.ebuild

Just a renamed boost-jam-3.1.4.ebuild

(From update of attachment 27305 [details])
Update for GraphicsMagick-1.05 and Boost-1.31 (Python 2.3)

Added to portage, thanks for the ebuild.

Please reopen this bug.  Chris Mayo supplied three files that need to be in
dev-python/pythonmagick/files for this ebuild to work.  Please include Jamfile,
Jamrules, and boost-build.jam in the portage tree.  (Note that in the future,
Gentoo probably ought to maintain a patch to Jamfile rather than replace it
wholesale, however.)

I second the last posters comment. This bug is NOT resolved. The files attached
to this bug are missing from the files directory.

I've added the missing files to the ebuild. 
Can you guys check that this ebuild is correctly working? 
Btw, the new pythonmagic 0.7 source code isn't available anymore from upstream page.

*** Bug 87552 has been marked as a duplicate of this bug. ***

Created an attachment (id=55296) [details]
pythonmagick development ebuild

The files are fine - pythonmagick compiles and installs. But I now get errors
like:

File "/usr/lib/python2.3/site-packages/PythonMagick/__init__.py", line 1, in ?
    import _PythonMagick
ImportError: libGraphicsMagick.so.0: cannot open shared object file: No such
file or directory

Whenever I run a program using it. I think it's something to do with upgrading
from GraphicsMagick 1.0 to 1.1. Even if you downgrade GraphicsMagick and
recompile PythonMagick it is then looking for the other version of the file,
libGraphicsMagick.so.1.

0.7 doesn't really exist they are just Windows binaries of the latest
development. Attached is a rough ebuild that grabs the latest source from the
subversion repository - I don't think there have been updates for a while. But
I get the same problem as above when I try and run programs using it.

Some more emerging and the missing library problems have gone away.

(I am using graphicsmagick-1.0.6 (PythonMagick was developed against 1.0, not sure what the effect of using 1.1 is) and:
dev-libs/boost-1.31.0
dev-util/boost-jam-3.1.9-r1)

N.B. now that I can get it to run again I found a new bug that stops text annotation from working #88058.