From: Alex Schuster <wonko@wonkology.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge --update - why doesn't it update my kde packages
Date: Wed, 5 May 2010 01:10:36 +0200 [thread overview]
Message-ID: <201005050110.37376.wonko@wonkology.org> (raw)
In-Reply-To: <4BE07D4E.7040504@konstantinhansen.de>
KH writes:
> Am 04.05.2010 21:41, schrieb Dale:
> > I have with-bdeps set in my make.conf so that it is enabled each
> > time. I just ran the command given above and it found over 40
> > packages that need to be upgraded. I'm not even going to claim that
> > I understand all the chicken scratch in that command but apparently
> > stuff needed to be upgraded on my system that was being missed.
If a deep @system @world upgrade with --with-bdeps=y does not upgrade the
packages, then I think that they are either unnecessary packages that
should be depcleaned, or they should go into the world file. This
update_orphans.sh script is nice and I used a similar one when I had the
problem that a world update did not work due to blockers or something, but
normally it should not be necessary. And I believe these problems should
better be fixed another way.
> For me it does try to update the same packages as --with-bdeps, but it
> tries to pull in like 39 new packages.
>
> How and where have you integrated with-bdeps in make.conf?
From /usr/share/portage/config/make.conf.example:
# EMERGE_DEFAULT_OPTS allows emerge to act as if certain options are
# specified on every run. Useful options include --ask, --verbose,
# --usepkg and many others. Options that are not useful, such as --help,
# are not filtered.
#EMERGE_DEFAULT_OPTS=""
I have it set like this: EMERGE_DEFAULT_OPTS="--with-bdeps y"
Wonko
next prev parent reply other threads:[~2010-05-04 23:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <eGm8V-4DS-1@gated-at.bofh.it>
2010-05-04 14:59 ` [gentoo-user] emerge --update - why doesn't it update my kde packages David W Noon
2010-05-04 15:48 ` KH
2010-05-04 19:41 ` Dale
2010-05-04 20:02 ` KH
2010-05-04 23:10 ` Alex Schuster [this message]
2010-05-05 0:23 ` Dale
2010-05-04 8:57 Helmut Jarausch
2010-05-04 9:43 ` Bert Swart
2010-05-04 10:09 ` Helmut Jarausch
2010-05-04 10:17 ` Bert Swart
2010-05-04 10:29 ` KH
2010-05-04 13:16 ` Alex Schuster
2010-05-04 16:19 ` Paul Hartman
2010-05-04 16:29 ` KH
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=201005050110.37376.wonko@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