On Wed, Dec 31, 2008 at 7:53 PM, Graham Murray <gra...@gmurray.org.uk> wrote: > "Michael P. Soulier" <msoul...@digitaltorque.ca> writes: > >> Sure enough, X no longer works. I'm following the instructions now, but... >> Don't you think the default action here should be to do nothing instead of >> breaking my system? > > I think that the default action should be that such 'breakages' should > be checked during the dependency building phase, a message displayed and > the emerge stop[0]. Then you could either mask the offending package or > issue a special flag[1] to emerge to acknowledge the 'problem' but > install/upgrade the package anyway. > > [0] As with package blockers. > > [1] A new flag, something like '--unsafe'
"[1]" there isn't as new as you might think, though it's a variable rather than a flag... I quote from the Busybox ebuild: "set env VERY_BRAVE_OR_VERY_DUMB=yes if this is realy what you want." "silly options will destroy your system" For any that haven't played with emerging Busybox to ROOT=/ and USE=make-symlinks, the text above is an excerpt from the message when the emerge chastises you ad calls 'die'. Incidentally... I'm going to go bug that typo (realy)... yay for Firefox's built in spell checking. -- Poison [BLX] Joshua M. Murphy
