public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Berntsen <alexander@plaimi.net>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Re: [PATCHES] Remove --autounmask, rename --autounmask-write to --autounmask
Date: Thu, 21 Nov 2013 15:23:50 +0100	[thread overview]
Message-ID: <528E1776.1030908@plaimi.net> (raw)
In-Reply-To: <pan$b8df1$65c2f13b$eda1a7d5$7486e042@cox.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 21/11/13 14:34, Duncan wrote:
> I read comment 10, and am objecting based on it
You have fundamentally misunderstood everything in it. Please reread it.

> 1) Because the dependency calculations take time, I normally use 
> --ask so I don't have to have portage redo those calculations if I
>  like what its telling me it's going to do.
> 
> 2) Under no circumstances do I want portage rewriting masks, etc,
> on its own, not even with config-protect.
> 
> 3) Despite that, I find the suggestions it makes saying what it 
> /thinks/ it needs unmasked useful -- I just want to write them to 
> the file I want, with the comment I want (sometimes with a bit 
> different atom, too), which portage wouldn't do.
All of this is irrelevant to my patches.

> 4) You're saying emerge --ask foo would write the config
No. Please read comment 10[0].

> 5) There needs to be a way to get portage's current emerge --ask 
> --autounmask foo (without --autounmask-write)
There is. This doesn't change in my patches. Please read the code or
comment 10[0].

> I'd tend to agree, but in that case, why are you wanting to do away
>  with the ability to have portage spit out its opinion, without 
> having portage actually do the write, while using --ask?
Because it can be done without --ask. See comment 10[0].


[0]  <https://bugs.gentoo.org/show_bug.cgi?id=481578#c10>
- -- 
Alexander
alexander@plaimi.net
http://plaimi.net/~alexander
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iF4EAREIAAYFAlKOF3YACgkQRtClrXBQc7XcYgD/bW0XXYgXwkA7CvtFVCphboxd
MQNdi8HTZ3SCP8N+mRIBAIEhlHJsmtLqhreJNNWc+0KeSOR0IaOoXz0J16kAjF8c
=Te1c
-----END PGP SIGNATURE-----


  reply	other threads:[~2013-11-21 14:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-21  9:21 [gentoo-portage-dev] [PATCHES] Remove --autounmask, rename --autounmask-write to --autounmask Alexander Berntsen
2013-11-21 11:19 ` [gentoo-portage-dev] " Duncan
2013-11-21 12:03   ` Alexander Berntsen
2013-11-21 13:34     ` Duncan
2013-11-21 14:23       ` Alexander Berntsen [this message]
2013-11-22  5:37         ` Duncan
2013-11-22  8:29           ` Alexander Berntsen
2013-11-21 16:30 ` [gentoo-portage-dev] " Paul Varner
2013-11-21 16:46   ` Alexander Berntsen
2013-11-21 21:05     ` Paul Varner
2013-11-21 20:06 ` Zac's status (Was: Re: [gentoo-portage-dev] [PATCHES] Remove --autounmask, rename --autounmask-write to --autounmask) Pacho Ramos
2013-11-22  8:51   ` Alexander Berntsen

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=528E1776.1030908@plaimi.net \
    --to=alexander@plaimi.net \
    --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