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