Gentoo Archives: gentoo-portage-dev

From: Wade Cline <wadecline@×××××××.com>
To: Zac Medico <zmedico@g.o>, "gentoo-portage-dev@l.g.o" <gentoo-portage-dev@l.g.o>
Subject: RE: [gentoo-portage-dev] [PATCH] Add --autounmask-write-retry feature.
Date: Mon, 13 Oct 2014 07:49:33
Message-Id: BAY178-W348A21EE0A5320BDD9BB64B5AC0@phx.gbl
In Reply to: Re: [gentoo-portage-dev] [PATCH] Add --autounmask-write-retry feature. by Zac Medico
1 That is correct, although I was not aware of it at the time.
2
3 Shortly after submitting the patch, Brian Dolbec gave me some
4 useful feedback but I have not yet taken the time to implement it.
5 From skimming e-mail headers, though, it looks like the autounmask
6 feature is undergoing changes, so I'll have to look at those
7 changes and re-base the code before the next revision.
8
9 Thank you,
10 Wade
11
12 ___________________________________________________________________
13 "If you say the same thing over and over again, it's brainwashing."
14
15
16 > Date: Sat, 11 Oct 2014 14:32:18 -0700
17 > From: zmedico@g.o
18 > To: gentoo-portage-dev@l.g.o; wadecline@×××××××.com
19 > Subject: Re: [gentoo-portage-dev] [PATCH] Add --autounmask-write-retry feature.
20 >
21 > On 05/19/2014 09:43 AM, Wade Cline wrote:
22 > > This patch allows users to re-attempt an emerge after USE flag changes
23 > > have been automatically written via --autounmask-write, allowing easier
24 > > installation of ebuilds when users are not concerned about USE flag
25 > > details. Previously, users would have needed to invoke emerge multiple
26 > > times.
27 > >
28 > > Implementation was choosen based off of what was possible for me to get
29 > > working at the time. Based on Portage 2.2.10_p25_p484922.
30 > > ---
31 >
32 > If I understand correctly, this works under the assumption that the user
33 > has CONFIG_PROTECT_MASK="/etc/portage" or something like that?
34 > Otherwise, it won't work, because the user needs to run etc-update or
35 > dispatch-conf. Right?
36 > --
37 > Thanks,
38 > Zac