-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 01/10/15 03:22 PM, Ciaran McCreesh wrote: > On Thu, 1 Oct 2015 21:11:22 +0200 Kristian Fiskerstrand > <k...@gentoo.org> wrote: >> On 10/01/2015 09:12 PM, Ciaran McCreesh wrote: >>> On Thu, 1 Oct 2015 15:08:00 -0400 Ian Stakenvicius >>> <a...@gentoo.org> wrote: >>>> Slotmove VDB updates *should* be allow slotmove-related >>>> changes to be excluded here too, but unfortunately with >>>> portage not doing updates to rdeps properly, at this time >>>> all rdeps will need to be revbumped when their RDEPEND >>>> changes. >>> >>> This is a severe misrepresentation of what the issue actually >>> is. >>> >> >> Thanks for pointing that out, would you please elaborate on >> what the issue actually is for the purpose of this discussion? > > Some people expect Portage to do the impossible when handling > slot moves, on the basis that with a superficial understanding it > looks like it could partially work in certain easy cases. Thus > "all rdeps will need to be revbumped when their RDEPEND changes" > is not an "at this time" thing at all, but a genuine > requirement. >
I think "for the purpose of this discussion" is the relevant point of K_F's question -- that is, is there a severe misrepresentation on the need to revbump all ebuilds of rdeps when a package changes its SLOT= ? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlYOi7UACgkQAJxUfCtlWe2LlgD+I6vLjXGDPfq1/ojscXVrMp0A jUHv4qE6Yl91mTqp1e8A/jWTkKJdqMB8y70jE7LdHZAHIRS4JvpOkW1UEQmHHxwe =ZOTx -----END PGP SIGNATURE-----
