public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Aaron Walker <ka0ttic@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Gentoo beeping at me!
Date: Wed, 24 Nov 2004 05:14:56 -0500	[thread overview]
Message-ID: <41A45F20.4040800@gentoo.org> (raw)
In-Reply-To: <20041123160916.0374b094@snowdrop.home>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ciaran McCreesh wrote:
| On Tue, 23 Nov 2004 10:55:14 -0500 Hasan Khalil <gongloo@gentoo.org>
| wrote:
| | AFAIK, there is no user documentation for most eclasses' options,
| | including this one. That's the whole problem IMO.
|
| Well... Most eclasses don't provide anything that the user should be
| concerned about... But, if someone wants to put this somewhere:
|
| To disable the pause which is sometimes displayed after messages when
| emerging a package, set EPAUSE_IGNORE="true" in /etc/make.conf. To
| disable the beeps which are sometimes made after messages, also set
| EBEEP_IGNORE="true".
|

IMO, it belongs in make.conf(5).

http://bugs.gentoo.org/show_bug.cgi?id=72325

- --
SEMPER UBI SUB UBI!!!!

[ Always wear underwater ]

Aaron Walker < ka0ttic@gentoo.org >	http://dev.gentoo.org/~ka0ttic/
Gentoo/BSD | cron | shell-tools		http://butsugenjitemple.org/~ka0ttic/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFBpF8gC3poscuANHARApuJAKC3sXViBkqrhLU7cLUGjvlDshFlbgCg5KMZ
tYUL6wCLmOp5aEcFxnw4BVY=
=3D2z
-----END PGP SIGNATURE-----

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2004-11-24 10:15 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23  1:43 [gentoo-dev] Gentoo beeping at me! Roman Gaufman
2004-11-23  1:51 ` Mike Frysinger
     [not found]   ` <E86D9DE1-3D06-11D9-A6F4-000A95D3E704@gentoo.org>
2004-11-23  4:33     ` Mike Frysinger
2004-11-23  4:38       ` Lina Pezzella
2004-11-23  4:45         ` Mike Frysinger
2004-11-23  7:38           ` Daniel Armyr
2004-11-23  8:14             ` Ciaran McCreesh
2004-11-23 14:38             ` Roman Gaufman
2004-11-23 15:55               ` Hasan Khalil
2004-11-23 16:09                 ` Ciaran McCreesh
2004-11-24 10:14                   ` Aaron Walker [this message]
2004-11-23 16:20                 ` Chris Gianelloni
2004-11-23 23:26                   ` Dan Meltzer
2004-11-24  2:15                     ` Chris Gianelloni
2004-11-24 10:08                       ` Aaron Walker
     [not found]                       ` <46059ce1041123200452e69415@mail.gmail.com>
2004-11-24 13:44                         ` Chris Gianelloni
2004-11-24 20:10                     ` Benjamin Schindler
2004-11-25  9:44                       ` Georgi Georgiev
2004-11-25 19:19                         ` Ed Grimm
2004-11-25 20:02                           ` Ciaran McCreesh
2004-11-26  2:25                           ` Georgi Georgiev
2004-11-26 10:17                             ` Ciaran McCreesh
2004-11-26 18:03                               ` Georgi Georgiev
2004-11-26 18:45                                 ` Dan Meltzer
2004-11-26 19:17                                   ` Ciaran McCreesh
2004-11-26 23:55                                 ` Ed Grimm

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=41A45F20.4040800@gentoo.org \
    --to=ka0ttic@gentoo.org \
    --cc=gentoo-dev@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