From: Ron Bickers <rbickers-list-gentoo-user@logicetc.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Heads-Up sys-lib/ss breaks Apps
Date: Fri, 8 Jul 2005 11:52:44 -0400 [thread overview]
Message-ID: <200507081152.44634.rbickers-list-gentoo-user@logicetc.com> (raw)
In-Reply-To: <1120801115.29226.58.camel@neuromancer.home.net>
On Fri July 8 2005 01:38 am, Ow Mun Heng wrote:
> Which is a huge bummer since most of us don't go checking the ebuilds
> for these specific lines. How I wish It would just abort and BLAST the
> Einfo on the screen for me to see the next day and decide to do it
> manually.
I have this concern as well. Also, when emerging multiple packages, the
helpful and sometimes necessary output at the end of each merge is easily
missed as the next package begins. It would be nice to at least have these
messages logged somewhere. Are they? Can they be without patching portage?
--
Ron
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-08 16:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 5:38 [gentoo-user] Heads-Up sys-lib/ss breaks Apps Ow Mun Heng
2005-07-08 6:04 ` Zac Medico
2005-07-08 6:28 ` [gentoo-user] Heads-Up sys-lib/com_err " Ow Mun Heng
2005-07-08 7:11 ` Zac Medico
2005-07-08 7:38 ` W.Kenworthy
2005-07-08 7:53 ` Ow Mun Heng
2005-07-08 15:56 ` Roy Wright
2005-07-09 11:21 ` Peter Ruskin
2005-07-09 12:04 ` Peter Ruskin
2005-07-10 1:24 ` Roy Wright
2005-07-08 15:52 ` Ron Bickers [this message]
2005-07-08 16:51 ` [gentoo-user] Heads-Up sys-lib/ss " Uwe Thiem
2005-07-08 17:47 ` kashani
2005-07-09 1:56 ` Allan Gottlieb
2005-07-10 1:41 ` Ow Mun Heng
2005-07-08 19:17 ` Rumen Yotov
-- strict thread matches above, loose matches on Subject: below --
2005-07-08 18:18 Nick Smith
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=200507081152.44634.rbickers-list-gentoo-user@logicetc.com \
--to=rbickers-list-gentoo-user@logicetc.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