Gentoo Archives: gentoo-portage-dev

From: Pacho Ramos <pacho@g.o>
To: gentoo-portage-dev@l.g.o
Subject: Re: [gentoo-portage-dev] [PATCH 1/3] emerge: Deprecate --autounmask
Date: Sun, 19 Jan 2014 08:01:41
Message-Id: 1390118493.24148.118.camel@belkin5
In Reply to: [gentoo-portage-dev] [PATCH 1/3] emerge: Deprecate --autounmask by Alexander Berntsen
1 El dom, 19-01-2014 a las 01:21 +0100, Alexander Berntsen escribió:
2 > Remove the --autounmask option from emerge. Please note that removing
3 > the option does not mean that the variable used for keeping track of
4 > autounmasking is not removed from depgraph.py.
5
6 If I understand the change correctly (I don't know much about python
7 but, but per the diff, looks like you are dropping the option and making
8 the code behave like it's always 'True'), seems that you are forcing
9 autounmask to be on always.
10
11 Even if I use this in all my systems (passing it in by default emerge
12 opts), I think we still need a way to disable it sometimes. For example,
13 I need that when portage shows me really strange error messages. I
14 remember this was an old bug related with backtracking, but can't find
15 it just now (it should contains quite a few duplicates) :S
16
17 I am referring to that kind of errors that reports the wrong package as
18 being the culprit of some conflict

Replies

Subject Author
Re: [gentoo-portage-dev] [PATCH 1/3] emerge: Deprecate --autounmask Alexander Berntsen <alexander@××××××.net>