public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] New ideas, USE database, sandbox & more
Date: Mon, 3 Dec 2001 10:28:28 -0600	[thread overview]
Message-ID: <20011203102828.B30257@chiba.3jane.net> (raw)
In-Reply-To: <20011203220147.D13834@swool.com>

On Mon, Dec 03, 2001 at 10:01:47PM +0800, Joshua Pierre wrote:

> This would be really cool, I imagine it would be hard to add to portage.
> (Comments drobbins?)

"emerge gcc" would be easy to add.  Not a priority for me atm.  Is it really
so hard to type "emerge sys-devel/gcc"?
> 
> > 5)Compile and install logs should be stored for future inspection.
> >   Should be realy simple to implement. Just redirect sub shell to 
> >   "| tee <logfilename>. Or even "> logfilename" if emerge called with
> >   --silent flag.
> 
> Again, this would be really good for backtracking failed builds.

There is a command called "script" that can be used to log everything that
happens on the console.  This logging issue comes up periodically, and
personally, I think it's easier to use our already existing command.  Type "man
script".  Basically, "script" gives you a new shell where everything is logged
to a typescript file.  When you exit the new shell, scripting is turned off.
The disadvantage of this approach is that scripting does not happen on a
per-package basis.  But I haven't seen any Gentoo Linux developers actually
requesting enhanced logging capabilities.  So again, not a high priority.

Best Regards,

-- 
Daniel Robbins                                  <drobbins@gentoo.org>
Chief Architect/President                       http://www.gentoo.org 
Gentoo Technologies, Inc.


  parent reply	other threads:[~2001-12-03 16:28 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03  1:06 [gentoo-dev] USE database? Zach Forrest
2001-12-03  7:41 ` AW: " Sebastian Werner
2001-12-03  9:13   ` Geert Bevin
2001-12-03 10:02     ` AW: " Sebastian Werner
2001-12-03 10:12       ` Geert Bevin
2001-12-03 11:05         ` AW: " Sebastian Werner
2001-12-03 11:05           ` Geert Bevin
2001-12-03 11:26             ` AW: " Sebastian Werner
2001-12-03 11:32   ` [gentoo-dev] New ideas, USE database, sandbox & more Vitaly Kushneriuk
2001-12-03 11:48     ` Geert Bevin
2001-12-03 12:55       ` Vitaly Kushneriuk
2001-12-03 14:01     ` Joshua Pierre
2001-12-03 16:06       ` Vitaly Kushneriuk
2001-12-03 16:28       ` Daniel Robbins [this message]
2001-12-03 18:00         ` Vitaly Kushneriuk
2001-12-03 16:48 ` [gentoo-dev] USE database? Daniel Robbins
2001-12-06  6:01   ` Mikael Hallendal
2001-12-06 18:12     ` Zach Forrest
2001-12-06 20:38       ` Mikael Hallendal
2001-12-06 22:33         ` Zach Forrest
2001-12-06 23:40           ` Daniel Robbins
2001-12-06 23:52             ` Zach Forrest
2001-12-07 19:28           ` Sebastian Werner
2001-12-07 21:39             ` Daniel Robbins
2001-12-07 21:43               ` Geert Bevin
2001-12-08  1:44               ` Mikael Hallendal

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=20011203102828.B30257@chiba.3jane.net \
    --to=drobbins@gentoo.org \
    --cc=gentoo-dev@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