On Monday 03 November 2003 02:16, Jon Portnoy wrote: > > ------------------------- > > Scenario 5: Ebuild speech > > ------------------------- > > On completion of merging the portage ebuild sleeps for ~15 seconds, the > > baselayout ebuild for ~10 seconds and even dev-sources sleeps for ~5 > > seconds whilst all these packages display messages. In my opinion, this > > is downright pointless. On a source distribution like this one > > especially > > Except that it sleeps for _very important messages_. Those timers are > there because people were totally missing those messages.
My understanding of the original posters dislike is not that beep-and-sleep happens, nor that it happens by default, but rather that the behaviour is hard coded into individual ebuilds in a way that makes it difficult to customise. I think we can reasonably debate whether beep-and-sleep is the best way of getting the users attention for these important messages, but I would be suprised if we didnt all agree that the current approach of putting beep-and-sleep in individual ebuilds is substandard. -- Toby Dickenson -- [EMAIL PROTECTED] mailing list
