-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 15/07/12 06:16 PM, Zac Medico wrote: > On 07/15/2012 03:08 PM, Doug Goldstein wrote: >> Is it valid to do something like: >> >> move media-plugins/mytharchive media-plugins/mythplugins move >> media-plugins/mythbrowser media-plugins/mythplugins move >> media-plugins/mythgallery media-plugins/mythplugins move >> media-plugins/mythgame media-plugins/mythplugins move >> media-plugins/mythmovies media-plugins/mythplugins move >> media-plugins/mythnews media-plugins/mythplugins move >> media-plugins/mythweather media-plugins/mythplugins > > No, that's not really how it's intended to be used. You'll probably > have to put blockers in media-plugins/mythplugins to block all the > old packages that install the same files.
Theoretically (i've done a quick test on this and it seems true) a single-"!" blocker is enough that one package will on upgrade replace all these others without user intervention being required (assuming these packages aren't in @world, of course), and it won't cause file collisions. Unrelatedly curious, why the package merge? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlAEG+cACgkQ2ugaI38ACPCz0QEAiuBnHl3Va2cHzUnUPT4eHFei kJXPBEnrsMq7jLX2H8IA/20zKcaGh+SsyTzh0jMauiTeh7zF1+PwLpcgJSpH0YS+ =BLip -----END PGP SIGNATURE-----
