From: Willie Wong <wwong@Princeton.EDU>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: java-config issues
Date: Mon, 7 Nov 2005 19:41:00 -0500 [thread overview]
Message-ID: <20051108004100.GB32694@princeton.edu> (raw)
In-Reply-To: <c3d5f3800511071248r47b23c15j6632a1213eee3b9b@mail.gmail.com>
On Mon, Nov 07, 2005 at 08:48:20PM +0000, Qian Qiao wrote:
> On 11/7/05, James <wireless@tampabay.rr.com> wrote:
> > Well using 'python-updater'
> > env-update && source /etc/profile && etc-update
> > and 'emerge -uD world'
> >
> > everything is fine now.....
> >
> > Where does one read about python-updater ?
>
> It was printed on the screen when you update your python package. Did
> you do your upgrades through a cron? Or did you do it non-attended?
>
> Please don't do that...
Can't resist: you left out one option. I do my updates unattended: I
sync, I look at what should be updated, set emerge up to run over
night to update those packages, and go to bed.
BUT! I did set PORT_LOGDIR in /etc/make.conf and I check the next
morning to see if there are any important messages from einfo or
ewarn.
To be honest, I can't quite imagine you staring at the screen for 2
bloody hours the next time you update glibc, or mozilla, or kde...
=D
Back on track for the OP: if you are root of a a box, then it is your
responsibility to make sure you see the warning messages produced from
the emerge.
W
--
I have a mind like a steel...animal catcher thingy.
Sortir en Pantoufles: up 5 days, 1:55
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-08 0:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 18:20 [gentoo-user] java-config issues James
2005-11-07 18:45 ` Michael Sullivan
2005-11-07 20:19 ` [gentoo-user] " James
2005-11-07 20:48 ` Qian Qiao
2005-11-08 0:41 ` Willie Wong [this message]
2005-11-08 2:00 ` Qian Qiao
2005-11-08 14:40 ` Allan Gottlieb
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=20051108004100.GB32694@princeton.edu \
--to=wwong@princeton.edu \
--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