Re: [gentoo-portage-dev] Re: [PATCH] Add emerge --autounmask-continue option (bug 582624)

2016-07-04 Thread Alexander Berntsen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 04/07/16 20:00, Zac Medico wrote: > I wasn't aware that there was an argument about that. I didn't argue it very heavily, but I do find it useful. > I'll be happy to send pushed emails. Thanks! - -- Alexander berna...@gentoo.org

Re: [gentoo-portage-dev] Re: [PATCH] Add emerge --autounmask-continue option (bug 582624)

2016-07-04 Thread Zac Medico
On 07/04/2016 05:17 AM, Alexander Berntsen wrote: > Never mind. I see that it's already pushed. I guess this is where I > continue to argue my case for "Pushed as [commit hash]" emails. I wasn't aware that there was an argument about that. I'll be happy to send pushed emails. -- Thanks, Zac

Re: [gentoo-portage-dev] Re: [PATCH] Add emerge --autounmask-continue option (bug 582624)

2016-07-04 Thread Zac Medico
On 07/04/2016 05:16 AM, Alexander Berntsen wrote: > Looks OK. But you've found a few bugs already. Maybe you'll find more. > I'd appreciate if you hold off until the end of the week before > pushing it confidently. I'm extremely confident in v2 of the patch. I don't expect that we'll find any

Re: [gentoo-portage-dev] Re: [PATCH] Add emerge --autounmask-continue option (bug 582624)

2016-07-04 Thread Alexander Berntsen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Never mind. I see that it's already pushed. I guess this is where I continue to argue my case for "Pushed as [commit hash]" emails. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG

Re: [gentoo-portage-dev] Re: [PATCH] Add emerge --autounmask-continue option (bug 582624)

2016-07-02 Thread Brian Dolbec
On Fri, 1 Jul 2016 22:40:47 -0700 Zac Medico wrote: > On 07/01/2016 03:46 PM, Zac Medico wrote: > > On 07/01/2016 12:37 AM, Zac Medico wrote: > >> @@ -327,6 +341,11 @@ def action_build(settings, trees, mtimedb, > >>display_missing_pkg_set(root_config, >

[gentoo-portage-dev] Re: [PATCH] Add emerge --autounmask-continue option (bug 582624)

2016-07-01 Thread Zac Medico
On 07/01/2016 03:46 PM, Zac Medico wrote: > On 07/01/2016 12:37 AM, Zac Medico wrote: >> @@ -327,6 +341,11 @@ def action_build(settings, trees, mtimedb, >> display_missing_pkg_set(root_config, e.value) >> return 1 >> >> +if success and

Re: [gentoo-portage-dev] Re: [PATCH] Add emerge --autounmask-continue option (bug 582624)

2016-07-01 Thread Brian Dolbec
On Fri, 1 Jul 2016 10:17:50 -0700 Zac Medico wrote: > On 07/01/2016 09:42 AM, Duncan wrote: > > Zac Medico posted on Fri, 01 Jul 2016 08:35:26 -0700 as excerpted: > > > >>> But if you genuinely think this is a good idea, and someone else > >>> on the team does too, I won't

[gentoo-portage-dev] Re: [PATCH] Add emerge --autounmask-continue option (bug 582624)

2016-07-01 Thread Zac Medico
On 07/01/2016 12:37 AM, Zac Medico wrote: > @@ -327,6 +341,11 @@ def action_build(settings, trees, mtimedb, > display_missing_pkg_set(root_config, e.value) > return 1 > > + if success and mydepgraph.need_config_reload(): > +

Re: [gentoo-portage-dev] Re: [PATCH] Add emerge --autounmask-continue option (bug 582624)

2016-07-01 Thread Zac Medico
On 07/01/2016 09:42 AM, Duncan wrote: > Zac Medico posted on Fri, 01 Jul 2016 08:35:26 -0700 as excerpted: > >>> But if you genuinely think this is a good idea, and someone else on the >>> team does too, I won't oppose it. We should make sure that we strongly >>> discourage its usage for regular

Re: [gentoo-portage-dev] Re: [PATCH] Add emerge --autounmask-continue option (bug 582624)

2016-07-01 Thread Alexander Berntsen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 01/07/16 18:42, Duncan wrote: > Perhaps rename the option so it makes perfectly clear the possible > consequences? Something like --autounmask-breakme, or > --auto-breakme ? No. - -- Alexander berna...@gentoo.org

[gentoo-portage-dev] Re: [PATCH] Add emerge --autounmask-continue option (bug 582624)

2016-07-01 Thread Duncan
Zac Medico posted on Fri, 01 Jul 2016 08:35:26 -0700 as excerpted: >> But if you genuinely think this is a good idea, and someone else on the >> team does too, I won't oppose it. We should make sure that we strongly >> discourage its usage for regular users. Perhaps your suggested manpage >>