Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 501656

Summary: sys-apps/portage: Impossible to have 2 type of subslot rebuild for 1 ebuild, one that always builds ruby's rmagick and another for SONAME
Product: Gentoo Linux Reporter: Pacho Ramos <pacho>
Component: Current packagesAssignee: Portage team <dev-portage>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Pacho Ramos gentoo-dev 2014-02-18 06:47:14 UTC
Otherwise it is not rebuilt when imagemagick is updated
 *  - /usr/lib64/libMagickCore-6.Q16.so.1
 *  - /usr/lib64/libMagickCore-6.Q16.so.1.0.0
 *  - /usr/lib64/libMagickWand-6.Q16.so.1
 *  - /usr/lib64/libMagickWand-6.Q16.so.1.0.0
 *  - /usr/lib64/libMagick++-6.Q16.so.2
 *  - /usr/lib64/libMagick++-6.Q16.so.2.0.0
 *      used by /usr/bin/inkscape (media-gfx/inkscape-0.48.4-r1)
 *      used by /usr/bin/inkview (media-gfx/inkscape-0.48.4-r1)

Thanks
Comment 1 Samuli Suominen (RETIRED) gentoo-dev 2014-02-18 07:14:46 UTC
I don't know about that, scarabeus added subslotting to ImageMagick only for auto-rebuilding the ruby rmagick
So only package that should have := for imagemagick should be that currently
Comment 2 Samuli Suominen (RETIRED) gentoo-dev 2014-02-18 07:18:15 UTC
Yep. Only rmagick is using :=. Since ImageMagick is using SLOT="0/${PV}" and is not based on SONAME, we can't use it for anything else but rmagick.
Thank scarabeus for that.
And thank Portage lacking feature for multiple different subslot's per ebuild.

dev-ruby/rmagick/rmagick-2.13.2.ebuild:RDEPEND=">=media-gfx/imagemagick-6.4.9:=[-hdri]"
dev-ruby/rmagick/rmagick-2.13.2-r1.ebuild:RDEPEND+=" >=media-gfx/imagemagick-6.4.9:=[-hdri]"
dev-ruby/rmagick/rmagick-2.13.2-r1.ebuild:DEPEND+=" >=media-gfx/imagemagick-6.4.9:=[-hdri]"
Comment 3 Samuli Suominen (RETIRED) gentoo-dev 2014-02-18 08:14:36 UTC

*** This bug has been marked as a duplicate of bug 462138 ***