Hello, Attached is imgSeek-0.6.4.ebuild. imgSeek is a GNU/Linux photo collection manager and viewer with content-based search and many other features. The query is expressed either as a rough sketch painted by the user or as another image you supply (or an image in your collection). More details at http://imgseek.sourceforge.net/ I suggest media-gfx/imgSeek. Python libraries will get installed to /usr/lib/python/site-packages/imgSeekLib and data files to /usr/imgSeekLib/. I believe I will have to change the distutils install script to install data on /usr/share/imgSeek or something. I'm also not sure about case issues with the ebuild name. This ebuild depend on Python, Imaging, ImageMagick and PyQt. Thanks. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 8451 [details] imgSeek 0.6.4 ebuild (New Package)
Should this go in dev-python? -- Stephen
Fails to start with me: $ imgSeek Starting imgSeek, please wait ... Traceback (most recent call last): File "/usr/lib/python2.2/site-packages/imgSeekLib/ImgDB.py", line 50, in ? import imgdb ImportError: libMagick-5.5.3.so.0: cannot open shared object file: No such file or directory Warning: Unable to load the C++ extension "imgdb.so" module. Make sure you installed imgSeek correctly, and email any install bug to "imgseek-devel@lists.sourceforge.net". Traceback (most recent call last): File "/usr/bin/imgSeek", line 27, in ? from imgSeekLib import * File "/usr/lib/python2.2/site-packages/imgSeekLib/ImgDB.py", line 54, in ? sys.exit() SystemExit imgSeek: Unable to find one of the modules required. Make sure imgSeek was installed properly. Looks like it's looking for libMagick-5.5.3.so.0, but I have /usr/lib/libMagick-5.5.4-Q16.so.0. Shouldn't it be looking for the symlink /usr/lib/libMagick.so?
imgdb.so is compiled with the options and switches provided by Magick++-config, so it ends up being linked with "-lMagick++", "-lMagick", "-ljbig", etc. I don't know why the imgdb.so you compiled ended up linked against an ImageMagick lib you don't even have on your system. I also believe gcc should resolve -lMagick to /usr/lib/libMagick.so which in its turn should be a symlink to an existing libMagick.so.x.x
Thanks for the information. Re-emerging imageMagick solved the problem. -- Stephen
remerging imagemagick apparently sorted it.