On Tue, 4 Nov 2003 19:43:14 -0500 Anthony de Boer wrote: > Jon Portnoy wrote: > > Many, many users use locate and many would complain if it was > > missing. > > On a box where only I have a shell, and never use slocate, it's not > needed and does get annoying when cron kicks in. This is probably a > very good example of something where people can agree to disagree. and > having a well-documented switch is a good thing. > > > ... rm /etc/cron.daily/locatedb.cron ... > > That does it, though chmod -x would be less fatal and more reversible. > I prefer to actually remove the package, though emerge insists on > wanting to put it back in when I update world, so we're having a > wrestling match. emerge inject is your friend > It's probably with good reason that I'm hesitant to muck with > profiles. > > > > 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. > > Except that *I* sleep for _very long compiles_. :-) I totally agree these sleeps are not the good way. We're waiting for the buffered messages to the end of the emerge process .. _that_ should solve the problem. (don't forget to remove the beeps too) > Also, I frequently emerge multiple packages at once, and only the > last's tail will still be on my screen when I come back. Even when > I'm awake, I rarely sit and watch the build go by. > > It might be good to have a batch flag to ebuild or in FEATURES that > says not to bother with sleep-and-beep because nobody is around. > > Some tools to find the Very Important Messages in PORT_LOGDIR's > copious output (I have 42 meg of build output there right now) would > be helpful. Ideally I'd be able to come back to the computer and > review all the messages from recently-completed builds. > > Storing the important messages in a release-notes file under > /var/db/pkg/*/*, so they're with the build permanently, might also be > a worthy idea. > > -- > Anthony de Boer > > -- > gentoo-dev@gentoo.org mailing list > -- Camille Huot - direct contact on #igoan at irc.freenode.net