Bug 533130 – Pretend unmasking for emerge --fetchonly

• Status: RESOLVED DUPLICATE of bug 329151
• Product: Portage Development

[Description Fedja Beader 2014-12-20 16:34:31 UTC]

It would be cool if emerge would "pretend" a package is unmasked if we are only fetching it.

Reproducible: Always

[Comment 1 Zac Medico 2014-12-20 16:42:51 UTC]

I don't think it's okay to change the default behavior, since that would be a major user-interface change. However, we could add a --masks=n option, or something like that.

[Comment 2 Fedja Beader 2014-12-20 16:46:13 UTC]

"good enough"

[Comment 3 Michał Górny 2014-12-20 16:50:34 UTC]

(In reply to Fedja Beader from comment #0)
> It would be cool if emerge would "pretend" a package is unmasked if we are
> only fetching it.
> 
> Reproducible: Always

Then it would catch newer versions even if an older version would be installed afterwards.

[Comment 4 Zac Medico 2015-01-13 17:43:47 UTC]

*** Bug 536494 has been marked as a duplicate of this bug. ***

[Comment 5 Fedja Beader 2016-03-27 00:05:00 UTC]

(In reply to Michał Górny from comment #3)
> 
> Then it would catch newer versions even if an older version would be
> installed afterwards.

Hmm.. from my understanding, emerge considers a masked package only if:
1) it was explicitly requested: emerge "=..." or ">..." or ...
2) it is needed to satisfy dependencies
3) architecture not supported
4) was selected, but LICENSE not allowed

Anything else? In the first two cases the masked version would be the one later installed, while in the other two would not be installed at all.

[Comment 6 Sam James 2023-01-10 12:39:18 UTC]

*** This bug has been marked as a duplicate of bug 329151 ***