Re: [gentoo-dev] libpng 1.6 upgrade and subslotting (and misuse of subslotting when there is also normal slotting)

[Ian Stakenvicius <axs@gentoo.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 05/04/13 09:52 PM, Ben de Groot wrote:
> On 6 Apr, 2013 4:46 AM, "Samuli Suominen" <ssuominen@gentoo.org 
> <mailto:ssuominen@gentoo.org>> wrote:
>> 
>> libpng 1.6 is in portage, but temporarily without KEYWORDS,
>> pending on
> testign and this conversion, help would be much appericiated with 
> converting the tree to use automatic rebuilds for the upgrade
>> 
>> Because there is binary-only SLOT="1.2" of libpng, none of these
>> are
> correct:
>> 
>> $ grep -r 'media-libs/libpng.*:=' */*/*.ebuild 
>> app-misc/tracker/tracker-0.14.4.ebuild:
>> >=media-libs/libpng-1.2:= app-misc/tracker/tracker-0.14.5.ebuild:
>> >=media-libs/libpng-1.2:= app-misc/tracker/tracker-0.16.0.ebuild:
>> >=media-libs/libpng-1.2:= app-misc/tracker/tracker-9999.ebuild:
>> >=media-libs/libpng-1.2:= media-gfx/digikam/digikam-3.0.0.ebuild:
>> media-libs/libpng:= media-gfx/digikam/digikam-3.1.0.ebuild:
>> media-libs/libpng:= 
>> media-plugins/gst-plugins-gl/gst-plugins-gl-0.10.3.ebuild: 
>> =media-libs/libpng-1.4:=
>> 
> media-plugins/gst-plugins-libpng/gst-plugins-libpng-1.0.5.ebuild:RDEPEND=">=media-libs/libpng-1.4:="
>>
>
> 
media-plugins/gst-plugins-libpng/gst-plugins-libpng-1.0.6.ebuild:RDEPEND=">=media-libs/libpng-1.4:="
>> www-client/chromium/chromium-27.0.1453.12.ebuild:
> media-libs/libpng:=
>> www-client/chromium/chromium-27.0.1453.3.ebuild:
> media-libs/libpng:=
>> www-client/chromium/chromium-9999-r1.ebuild:
>> media-libs/libpng:=
>> 
>> They should all be :0= to avoid matching the :1.2 SLOT.
>> 
>> Plus some hundreds are completely without subslotting:
>> 
>> $ grep -r 'media-libs/libpng' */*/*.ebuild |grep -v ':.*=' output
>> -> http://bpaste.net/show/89268/
>> 
>> Thanks, Samuli
>> 
> 
> This would be a good opportunity to use the latest eapi in all
> those packages. Would adding the :0= slot operator, and upping the
> eapi, warrant a revbump tho, or can we simply do it “in place"?
> 

Revbump -- very important in this case, as the slot-operator dep
(iirc) does not take effect to allow sub-slot-triggered until after a
version with the slot-operator has been emerged.

So we want users to re-emerge packages either at the same time
libpng-1.6 hits the tree, or beforehand so that they will be triggered
for rebuild when libpng-1.6 hits.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iF4EAREIAAYFAlFfhe4ACgkQ2ugaI38ACPC3/QD/UZp5DZTNjVcrEgbIWHjqS4W7
yQIYDQtqQnenC04hodsA/0AIvZH0+fvUtuqyxGX8tvBmHyPOLNjda2iL3Mtp98Sy
=O7qD
-----END PGP SIGNATURE-----