From: Pacho Ramos <pacho@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:32:29 +0100 [thread overview]
Message-ID: <1390127549.24148.144.camel@belkin5> (raw)
In-Reply-To: <52DBA79D.6000103@plaimi.net>
El dom, 19-01-2014 a las 11:23 +0100, Alexander Berntsen escribió:
> On 19/01/14 09:01, Pacho Ramos wrote:
> > If I understand the change correctly (I don't know much about
> > python but, but per the diff, looks like you are dropping the
> > option and making the code behave like it's always 'True'), seems
> > that you are forcing autounmask to be on always.
> You do not understand it correctly. It makes --ask imply
> --autounmask-write.
Ah, nice :)
>
> > Even if I use this in all my systems (passing it in by default
> > emerge opts), I think we still need a way to disable it sometimes.
> There is. Regardless of whether you mean (current) --autounmask or
> (current) --autounmask-write behaviour.
>
> emerge --ask foo # This won't -write
> emerge --autounmask --pretend foo # Same as the above
> emerge --ask --pretend foo # This won't even offer the suggestions
>
> Please see [0] for more information.
>
> [0] <https://bugs.gentoo.org/show_bug.cgi?id=481578#c10>
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 :( )
next prev parent reply other threads:[~2014-01-19 10:32 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 [this message]
2014-01-19 10:47 ` Alexander Berntsen
2014-01-19 16:49 ` Mike Gilbert
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=1390127549.24148.144.camel@belkin5 \
--to=pacho@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