-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 07 Jun 2012 15:14:03 -0400 Ian Stakenvicius <a...@gentoo.org> wrote: > How is the case of something like libpng going to be handled, where we > only support one API (and so only one SLOT)? Either in the proposed > ABI_SLOT thing or when using slot operators?
Ideally, by you putting in the work and supporting more than one API, since doing so vastly improves the user experience. Failing that, SLOT plus blockers. Then if it turns out that really doesn't work (and it's not just developers being utterly lazy), either ABI_SLOT or parts in a future EAPI. > For the slot-operator case, will every consumer of libpng be forced to > change their dep to libpng:= to ensure they get rebuilt when libpng > bumps from 1.5 to 1.6?? Every consumer of libpng that wants to improve from the current situation, yes. - -- Ciaran McCreesh -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAk/Q/dMACgkQ96zL6DUtXhFlgQCaAr/9xTL8/bwTHbqud5ETo1fN T64An077XiZVmdP+/76KBTdRVlaDa4U2 =se/J -----END PGP SIGNATURE-----
