From: Balaji Srinivasan <BSrinivasan@extremenetworks.com>
To: "'tberman@gentoo.org'" <tberman@gentoo.org>, gentoo-dev@gentoo.org
Subject: RE: [gentoo-dev] A nice idea to improve portage
Date: Tue, 10 Jun 2003 13:15:06 -0700 [thread overview]
Message-ID: <3A96A5B2A1D8AB46B99849DDF1F0BF1E2284F1@sc-msexch-07.extremenetworks.com> (raw)
I agree too...having this in etc-update would be good.
Balaji
-----Original Message-----
From: Todd Berman [mailto:tberman@gentoo.org]
Sent: Tuesday, June 10, 2003 1:03 PM
To: gentoo-dev@gentoo.org
Subject: RE: [gentoo-dev] A nice idea to improve portage
On Tue, 2003-06-10 at 14:46, John Robinson wrote:
> On Tue, 2003-06-10 at 14:16, Balaji Srinivasan wrote:
> > A better idea would be if portage wrote those messages to a file and
we
> > could view it when we wanted. ie. We could have a showEbuildMessages
or some
> > such program that showed all those messages and allowed you to ack
each one.
> > I think this would be pretty useful as normally when i am fixing
things i
> > dont have time to fix all of it in one shot...
>
> I agree; that would be an excellent idea. I would, however, at least
be
> in favor of portage printing something in red at the end of an emerge
> stating that the file had been updated and needed to be looked at;
> better, if it would print the (newly added) contents of the file. Some
> of the messages printed are about crucial things that need to be done,
> often configuration changes; leaving them to be read only if one feels
> like it might leave people thinking that the messages there don't
apply
> to them.
>
> - John
Just a quick note. I agree completely that portage must somehow output
this information after a massive emerge, or store it somewhere, however,
I question the sanity of yet another small utility. We already have
etc-update, env-update, modules-update and a host of other 'small'
applications. In my experience helping people on #gentoo, one of the
most common problems is the average new gentoo user's lack of awareness
of the existence of these small helper applications.
Integrating this with etc-update or another -update application seems
like a far better idea than just writing another script.
In fact, the idea of replacing all of said applications with ONE
gentoo-update seems like something that should be approached in the near
future. Even if gentoo-update is just a shell script that calls other
shell scripts.
--Todd
--
gentoo-dev@gentoo.org mailing list
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2003-06-10 20:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 20:15 Balaji Srinivasan [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-10 18:16 [gentoo-dev] A nice idea to improve portage Balaji Srinivasan
2003-06-10 18:36 ` Marius Mauch
2003-06-10 18:46 ` John Robinson
2003-06-10 20:02 ` Todd Berman
[not found] ` <1055271494.8194.8.camel@devweb>
2003-06-10 20:11 ` John Robinson
2003-06-10 14:25 [gentoo-dev] ebuild question MAL
2003-06-10 15:40 ` [gentoo-dev] A nice idea to improve portage MooktaKiNG
2003-06-10 16:07 ` Matthew Kennedy
2003-06-10 18:05 ` John Robinson
2003-06-10 20:20 ` Philippe Lafoucrière
2003-06-11 3:18 ` Luke Graham
2003-06-11 5:10 ` Bill Kenworthy
2003-06-10 21:56 ` MooktaKiNG
2003-06-10 21:42 ` Zach Forrest
2003-06-10 23:26 ` Kumba
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=3A96A5B2A1D8AB46B99849DDF1F0BF1E2284F1@sc-msexch-07.extremenetworks.com \
--to=bsrinivasan@extremenetworks.com \
--cc=gentoo-dev@gentoo.org \
--cc=tberman@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