Just found this gem and saw that there's a newer version available. Did a rename of the ebuild, seems to work fine. One minor (silly, really) note: Some of the wrapper bash scripts, such as /usr/bin/resize_image assume sys-devel/bc is installed.
Sorry, not "resize_image" – it should be "shrink_width"
Created attachment 322655 [details] vips-7.30.1.ebuild Here is an ebuild for the latest version, 7.30.1, which was released today. I also have a version including openslide support, which was added a few versions ago, but I didn't include that here since openslide is not in the official portage tree. Both ebuilds are on my github repo (https://github.com/speckins/usr-local-portage) if anyone needs that.
Created attachment 371584 [details] vips-7.38.5.ebuild Updated ebuild. Upgrade to EAPI=5 and python-single-r1 eclass.
Created attachment 371586 [details] metadata.xml Description of new USE flags.
Created attachment 427752 [details, diff] Updated ebuild to version 8.2.2 Update to EAPI 6 Add dependency on dev-libs/gobject-introspection to work around automagic dependency Always enable python vips8 overrides when USE=python
Created attachment 427754 [details, diff] Updated metadata.xml
For vips8, are these flags compatible? --with-python --enable-pyvips8 I thought the former made bindings for python 2. Since I want the bindings for python 3.5, I've been using --without-python. Also because the build fails for python 3.5 if I don't.
Thanks for testing! Indeed the vips7 bindings seem to be incompatible with python 3. So maybe add a "pyvips8" use flag for the vips8 bindings. The "python" use flag which will stand for the old vips7 bindings should then collide with $(python_gen_useflags 'python3*'). If everything works fine for you with python 3.5, we can also add that to PYTHON_COMPAT. Does that seems sensible? Feel free to create a corrected ebuild yourself. (There is documentation for the used eclass at https://devmanual.gentoo.org/eclass-reference/python-single-r1.eclass/index.html .) With a pull request this should get fixed soon.
Created attachment 428008 [details] Corrected vips-8.2.2.ebuild
Created attachment 428010 [details, diff] force_version_for_Vips.py.patch
Okay, I've submitted an updated ebuild. We could use "python" and "pyvips8", but it seems like it would be more user-friendly to just use "python", even if that makes the ebuild more complicated. I'm not an expert at this, so it's totally possible there's an error somewhere.
vips-7.38.5 is in the tree now (see bug 453810). I'll take a look at 8.3 update if I'll find some time, not now :/
Quick note: vips has been updated to version 8.4 just briefly after Andrew's post :) and is currently at 8.4.5. The 8.4.5 version can be built with the provided ebuild after a version bump and removing the force-version-patch.
Created attachment 466770 [details] vips-8.4.5.ebuild
Created attachment 466772 [details, diff] vips-8.4.5-force_version.patch
I've updated the ebuild and my patch, which is still necessary to suppress the version warning. Note that for macOS, I also needed Bug 612378.
I know this bug is old, but I'll request the same, current stable is vips 8.6, the emerge vips fails because it can't find the 7.38.5 anymore since it was released in 2012! we need a bump here
VIPS has moved to github, and it's homepage is now https://jcupitt.github.io/libvips/ I'll attach an ebuild for VIPS-8.6.0 with the new locations. It builds fine for me with latest imagemagick.
Created attachment 511830 [details] vips-8.6.0.ebuild
Created attachment 511832 [details, diff] vips-8.6.0-force_version.patch
Do you want to proxy maintain vips and nip2? https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers I remember last time we were able to get it bumped but, later, the problem reappeared as nobody was really maintaining it and bumping it
Gone.
