From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Question about difference between emerge --update world and emerge vigra
Date: Thu, 25 Sep 2008 18:32:24 +0000 (UTC) [thread overview]
Message-ID: <loom.20080925T181937-967@post.gmane.org> (raw)
In-Reply-To: 6142e6140809250851r45d271b2y600fcddd64cd2550@mail.gmail.com
Daniel Pielmeier <daniel.pielmeier <at> googlemail.com> writes:
> > to 'clean' the world file, in addition to what you have stated above?
> [1] http://bugs.gentoo.org/show_bug.cgi?id=172611
> Daniel
Hello Daniel,
What you have told me looks interesting. However, for now, I'm going
to clean up the critical systems with a more brute force approach,
as Neil has suggested. I cannot afford to wack these systems nor
have them reinstalling tons of software......
However, I am going to get workstation a non-critical workstation,
polluted the world file and try the python scripts a few times, to
develop an opinion or hack on it a bit.
udept seems like a good idea, it's ashame it has been orphaned. I'm
looking for a more stable (supported) solution for the long term.
udept does not seem to offer that, unless somebody picks it up
to maintain it. Who knows maybe one of the devs is working on a
better, long term solution.
Surely many folks would benefit from a formal, systematic approach
to cleaning the world file? I know every now and then, when a gentoo
workstation gives me fits, I just emerge and unemerge things until
it's happy (while multitasking too much). Often this leads to
a polluted world file....... because I do not follow closely to
the process details (distracted) during the repair-episode.
Thanks for the input.
James
next prev parent reply other threads:[~2008-09-25 18:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 4:05 [gentoo-user] Question about difference between emerge --update world and emerge vigra SOrCErEr
2008-09-25 5:13 ` Thomas Kahle
2008-09-25 6:16 ` Volker Armin Hemmann
2008-09-25 5:24 ` Marc Joliet
2008-09-25 6:24 ` Alan McKinnon
2008-09-25 9:54 ` SOrCErEr
2008-09-25 10:12 ` Vladimir Rusinov
2008-09-25 10:26 ` Alan McKinnon
2008-09-26 3:56 ` SOrCErEr
2008-09-25 10:23 ` Neil Bothwick
2008-09-25 10:27 ` Daniel Pielmeier
2008-09-25 15:08 ` [gentoo-user] " James
2008-09-25 15:29 ` Neil Bothwick
2008-09-25 15:51 ` Daniel Pielmeier
2008-09-25 18:32 ` James [this message]
2008-09-29 20:33 ` Daniel Pielmeier
2008-09-30 11:28 ` Paul Stear
2008-09-30 12:32 ` Daniel Pielmeier
2008-09-25 20:15 ` Alan McKinnon
2008-09-25 20:55 ` Paul Hartman
2008-09-25 21:43 ` Neil Bothwick
2008-09-25 21:59 ` Alan McKinnon
2008-09-25 22:53 ` Neil Bothwick
2008-09-25 15:51 ` [gentoo-user] " Hilco Wijbenga
2008-09-25 20:38 ` 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=loom.20080925T181937-967@post.gmane.org \
--to=wireless@tampabay.rr.com \
--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