From: Sascha Lucas <sascha.lucas@rus.uni-stuttgart.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Is binary emerge equivalent to source emerge?
Date: Thu, 8 Sep 2005 01:07:36 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.63.0509080101480.7596@tragbb.ehf.hav-fghggtneg.qr> (raw)
In-Reply-To: <431F4FBE.7090203@gmail.com>
> I've also had problems with --usepkg. When it gives me problems, as a
> workaround, I force emerge to do what I want with emerge --usepkgonly
> --nodeps --oneshot for each and every binpkg that I want merged. If I think
> that this may have broken something then afterwards I use "revdep-rebuild -p"
> to check linking integrity.
thats nearly the same like I do: emerge --usepkg --oneshot binpkgs.
So I assume, I'm not alone with this problem (--newuse & --usepkg & -uD).
The question is, is there a missunderstanding or a bug?
Sascha.
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-09-07 21:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 18:45 [gentoo-user] Is binary emerge equivalent to source emerge? Ian Clowes
2005-09-07 21:39 ` Sascha Lucas
2005-09-07 20:38 ` Zac Medico
2005-09-07 23:07 ` Sascha Lucas [this message]
2005-09-07 22:56 ` Zac Medico
2005-09-08 14:04 ` Sascha Lucas
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=Pine.LNX.4.63.0509080101480.7596@tragbb.ehf.hav-fghggtneg.qr \
--to=sascha.lucas@rus.uni-stuttgart.de \
--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