On 11/21/2010 05:27 PM, Delian Xu wrote: > For example, > Sometime when you install or update a package, it would failed by 'masked' > reasons and you have to deal with the failure > (Though you can use a auto-unmask tool here). However, users would hope > the Portage / emerge system give an option > to chose Y or N like this: > xxx lines of information and warnings about masked package, > Would you like to unmask the package and continue the installation? > [Y/N]: > > This would be much better for all users. (It is just an example.)
In portage-2.1.9 there's a new --autounmask option. If you like it you can use EMERGE_DEFAULT_OPTS to enable it by default in make.conf. There are a couple of related feature requests that I should also mention. Bug #258371 [1] requests the ability to automatically satisfy USE dependencies. This would be similar to having --autounmask enabled by default, but without requiring you to edit your config files. Bug #345775 [2] requests an option for --autounmask to automatically edit config files. Difficulty in resolving USE dependencies is a very common complaint. For example, I recently dealt with a user venting similar frustration to yours on bug #345175 [3]. It's worth mentioning that that there may be a lot of cases in which we can use IUSE defaults to satisfy reverse USE dependencies, without add adding any bloat. I would encourage ebuild developers to look for opportunities like this whenever adding USE dependencies. [1] http://bugs.gentoo.org/show_bug.cgi?id=258371 [2] http://bugs.gentoo.org/show_bug.cgi?id=345775 [3] http://bugs.gentoo.org/show_bug.cgi?id=345175 -- Thanks, Zac
