public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH 1/3] emerge: Deprecate --autounmask
Date: Sun, 19 Jan 2014 11:49:59 -0500	[thread overview]
Message-ID: <CAJ0EP408ncVB5zMF92upG+eQ0K2JT8WJbchm3XJFzrWj=c2_sw@mail.gmail.com> (raw)
In-Reply-To: <52DBAD46.1050200@plaimi.net>

On Sun, Jan 19, 2014 at 5:47 AM, Alexander Berntsen
<alexander@plaimi.net> wrote:
> On 19/01/14 11:32, Pacho Ramos wrote:
>> Then, I guess "-ap" would be the equivalent of --autounmask=n and
>> should behave in the same way, right? In that case, no problem
>> (even if I think we should document this since using --ask
>> --pretend at the same time doesn't look so intuitive to me :( )
> Since --ask implies --autounmask, the following are all the same for
> autounmask-purposes:
>
> emerge --pretend --ask foo
> emerge --pretend --autounmask foo
>
> As for "emerge --autounmask=n foo", This will actually spit out the
> suggestions, just not ask to write them.
>
> While playing with this, I discovered a possible misbehaviour though.
> With "emerge --ask --autounmask=n", --ask takes precedence to
> - --autounmask=n. Maybe it shouldn't. But this can always be changed.

Please give me a way to shut off autounmask entirely no mater what
other options I pass to emerge. Tying it to --ask with no way to
disable it is not acceptable.

Generating the unmask entries can cause quite a performance hit, and
often causes portage to come up with nonsensical solutions when an
error message would be much more helpful.


  reply	other threads:[~2014-01-19 16:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-19  0:21 [gentoo-portage-dev] [PATCH 1/3] emerge: Deprecate --autounmask Alexander Berntsen
2014-01-19  0:21 ` [gentoo-portage-dev] [PATCH 2/3] emerge: Rename --autounmask-write to --autounmask Alexander Berntsen
2014-01-19  2:14   ` Mike Gilbert
2014-01-19  2:15     ` Alec Warner
2014-01-19 10:18     ` Alexander Berntsen
2014-01-19  9:20   ` Mike Frysinger
2014-01-19 10:48     ` Alexander Berntsen
2014-01-20  5:45       ` Mike Frysinger
2014-01-19  0:21 ` [gentoo-portage-dev] [PATCH 3/3] emerge: Make --autounmask=y if --ask=y Alexander Berntsen
2014-01-19  8:01 ` [gentoo-portage-dev] [PATCH 1/3] emerge: Deprecate --autounmask Pacho Ramos
2014-01-19 10:23   ` Alexander Berntsen
2014-01-19 10:26     ` Alexander Berntsen
2014-01-19 10:32     ` Pacho Ramos
2014-01-19 10:47       ` Alexander Berntsen
2014-01-19 16:49         ` Mike Gilbert [this message]
2014-01-19 18:27           ` Alexander Berntsen
2014-01-25 19:07           ` Alexander Berntsen
2014-01-27 22:00             ` Tom Wijsman
2014-01-27 22:13               ` Alexander Berntsen
2014-01-27 22:26                 ` Tom Wijsman
2014-01-27 22:54                   ` Alexander Berntsen
2014-01-25  3:10         ` Brian Dolbec

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ0EP408ncVB5zMF92upG+eQ0K2JT8WJbchm3XJFzrWj=c2_sw@mail.gmail.com' \
    --to=floppym@gentoo.org \
    --cc=gentoo-portage-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox