From: Alex Schuster <wonko@wonkology.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Multiple package instances within a single package slot
Date: Sat, 5 Oct 2013 20:30:36 +0200 [thread overview]
Message-ID: <20131005203036.2e883e8a@weird.wonkology.org> (raw)
In-Reply-To: <20131005190218.3a3db9af@digimed.co.uk>
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
next prev parent reply other threads:[~2013-10-05 18:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 10:50 [gentoo-user] Multiple package instances within a single package slot Alex Schuster
2013-10-04 11:01 ` Alan McKinnon
2013-10-04 11:51 ` Kerin Millar
2013-10-04 15:40 ` Alex Schuster
2013-10-04 19:39 ` Alan McKinnon
2013-10-05 15:59 ` Alex Schuster
2013-10-05 16:22 ` Bruce Hill
2013-10-05 19:51 ` Alan McKinnon
2013-10-05 18:02 ` Neil Bothwick
2013-10-05 18:30 ` Alex Schuster [this message]
2013-10-05 19:53 ` Alan McKinnon
2013-10-05 20:35 ` Neil Bothwick
2013-10-06 10:09 ` Helmut Jarausch
2013-10-06 22:01 ` Alex Schuster
2013-10-06 22:42 ` Neil Bothwick
2013-10-04 11:56 ` Neil Bothwick
-- strict thread matches above, loose matches on Subject: below --
2013-03-05 23:21 Valmor de Almeida
2013-03-06 1:36 ` Matt Joyce
2013-03-06 3:46 ` Walter Dnes
2013-03-06 6:39 ` Alan McKinnon
2013-03-06 20:25 ` Valmor de Almeida
2013-03-06 21:17 ` Alan McKinnon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131005203036.2e883e8a@weird.wonkology.org \
--to=wonko@wonkology.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox