On August 20, 2012 15:27:54 Volker Armin Hemmann wrote: > Am Montag, 20. August 2012, 01:00:34 schrieb Reinhard Kotucha: > > On 2012-08-19 at 01:02:24 +0200, Volker Armin Hemmann wrote: > > > Am Sonntag, 19. August 2012, 00:37:36 schrieb Reinhard Kotucha: > > > > emerge --update --pretend > > > > > > why pretend? > > > > Because whenever I see that there is an Xorg update, I nowadays make a > > full backup before I do the actual update. > > that is what --ask is made for ;)
Nothing wrong with --pretend. I use it religiously for a couple of reasons. One is that when I want --quiet-build off, I can keep a complete list of the packages being merged in another screen tab, in case something fails. The other is that I don't want "emerge --ask" littering my emerge.log with stuff like this while I'm messing with USE flags, keywords, etc. and not actually committing to any emerges: 1345531458: Started emerge on: Aug 20, 2012 23:44:18 1345531458: *** emerge --ask --binpkg-respect-use=y --quiet-build=n --verbose --quiet-unmerge-warn extreme-tuxracer 1345531466: *** exiting unsuccessfully with status '130'. 1345531466: *** terminating. Getting back to the actual topic :) I've noticed that more and more packages are getting pkg_pretend() checks so that ebuilds can abort before the build starts if something is missing, e.g. missing kernel modules or in the case of Xorg, gcc being too old. This might be what you're asking for, in a way. Cheers, Bryan
