On 03/15/2017 03:32 PM, Brian Dolbec wrote:
> On Mon, 27 Feb 2017 20:33:28 +0200
> Alexandru Elisei wrote:
>
>> I was working on emerge --sync and my test repo configuration
>> generated several warning messages. Finding the exact location where
>> the warnings was
On 08/13/2017 04:37 PM, M. J. Everitt wrote:
> On 12/08/17 19:08, Zac Medico wrote:
>> The option prevents --autounmask from making changes to
>> package.accept_keywords. This option does not imply
>> --autounmask-keep-masks, so --autounmask is still allowed
>> to create package.unmask changes
On 08/13/2017 05:23 PM, M. J. Everitt wrote:
> On 14/08/17 01:19, Zac Medico wrote [excerpted]:
>> You'll get the same result as --autounmask-use-only if you use
>> --autounmask-keep-keywords together with --autounmask-keep-masks.
>>
>> This way, we can also add --autounmask-keep-license and
>>
On 08/13/2017 07:00 PM, M. J. Everitt wrote:
> Interesting .. I'm sure I shied away from that option for some reason
> ... wonder if zmedico can shed some light on the difference between the
> new options and the old, apart from some added flexibility ...
The --autounmask-keep-keywords option
On 12/08/17 19:08, Zac Medico wrote:
> The option prevents --autounmask from making changes to
> package.accept_keywords. This option does not imply
> --autounmask-keep-masks, so --autounmask is still allowed
> to create package.unmask changes unless the
> --autounmask-keep-masks is also
On 14/08/17 01:19, Zac Medico wrote [excerpted]:
> You'll get the same result as --autounmask-use-only if you use
> --autounmask-keep-keywords together with --autounmask-keep-masks.
>
> This way, we can also add --autounmask-keep-license and
> --autounmask-keep-use options if we want, and the
M. J. Everitt posted on Mon, 14 Aug 2017 00:37:45 +0100 as excerpted:
> My use-case consists of the scenario where I do not *ever* wish Portage
> to modify my /etc/portage/package. files, preferring to do
> this myself manually with a personal naming scheme which defines which
> target packages