Re: [gentoo-user] Multiple package instances within a single package slot

[Alan McKinnon]

On 05/10/2013 20:30, Alex Schuster wrote:
> Neil Bothwick writes:
>
>> On Sat, 5 Oct 2013 17:59:52 +0200, Alex Schuster wrote:
>>
>>> No, there is something wrong here. When I updated portage, it also
>>> remerged libreoffice. Upgrading claws-mail updated
>>> dev-libs/libdbusmenu and dev-libs/libindicate, and wanted to remerge
>>> libreoffice, which I avoided.
>>> Next, I updated chromium, which also remerged libreoffice. Again.
>>>
>>> And whatever package I try to update, emerge wants to remerge
>>> libreoffice. Happens with all the packages I tried, which are
>>> adobe-flash, python, zsh, xterm.
>>
>> If portage believes LO needs to be rebuilt, it will try to do so
>> whichever packages you are emerging, just let it happen.
>
> I already did that, twice, when updating portage and chromium. emerge
> still wants to remerge libreoffice whenever I upgrade a package.
>
>> With a suitable
>> --jobs setting, portage will emerge all the other packages before LO is
>> done.
>
> No, at least with portage, the installation happened after libreoffice was
> installed.
>
> weird ~ # emerge -1uaj portage
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild  r  U  ] app-office/libreoffice-4.1.2.2-r1 [4.1.2.2]
> [ebuild     U  ] sys-apps/portage-2.2.7 [2.2.0_alpha188]
> [...]
>>>> Emerging (1 of 2) app-office/libreoffice-4.1.2.2-r1
>>>> Emerging (2 of 2) sys-apps/portage-2.2.7
>>>> Installing (1 of 2) app-office/libreoffice-4.1.2.2-r1
>>>> Installing (2 of 2) sys-apps/portage-2.2.7
>>>> Jobs: 2 of 2 complete            Load avg: 3.06, 2.76, 2.63
>
> 	Alex
>


Now that you have upgraded portage, does this behaviour (always wanting
to rebuild LO) still happen?



-- 
Alan McKinnon
alan.mckinnon@×××××.com