| 1 |
On Wed, May 29, 2019 at 6:37 PM <n952162@×××.de> wrote: |
| 2 |
> |
| 3 |
> The next section of the response to my attempt to update portage is a long list of packages, each terminated with a "(masked by: something or other)". |
| 4 |
> |
| 5 |
> What does that tell me. If it's masked, it shouldn't be available, right? But, I've got it: |
| 6 |
> |
| 7 |
> - virtual/perl-parent-0.234.0-r1::gentoo (masked by: package.mask) |
| 8 |
> |
| 9 |
> ls virtual/perl-parent/perl-parent-0.234.0-r1.ebuild |
| 10 |
> virtual/perl-parent/perl-parent-0.234.0-r1.ebuild |
| 11 |
> |
| 12 |
> Can I get rid of it? Is perl-parent always masked? |
| 13 |
> |
| 14 |
|
| 15 |
I think one of the issues here is that you might be running a bit with |
| 16 |
scissors. |
| 17 |
|
| 18 |
It seems like you might be using package.keywords, and now you're |
| 19 |
dealing with package masks. |
| 20 |
|
| 21 |
Portage will let you override just about anything, but those default |
| 22 |
behaviors all exist for a reason and you can easily end up painting |
| 23 |
yourself into a corner. Overriding keywords is something that isn't |
| 24 |
too unsafe to do once you know what you're doing, but if you're doing |
| 25 |
it a lot it can get out of hand (adding keywords for one package can |
| 26 |
require 3 more, and if you keep that up it can really get out of |
| 27 |
hand). If you're overriding keywords frequently perhaps you should be |
| 28 |
running the testing branch in the first place, etc. |
| 29 |
|
| 30 |
Overriding masks is something that should only be done if you REALLY |
| 31 |
know what you're doing. If something is masked it might contain |
| 32 |
security vulnerabilities, or it might be going away. The consequences |
| 33 |
of the former are obvious. If it is going away then you're going to |
| 34 |
be fighting to keep things working because the next step will be |
| 35 |
removal and other packages will start being modified to not work with |
| 36 |
the old approach. |
| 37 |
|
| 38 |
Basically, any setting you put in /etc/portage is something you're |
| 39 |
going to have to work to maintain, so you should be doing whatever you |
| 40 |
can to minimize this. By all means speak up on the list about "I'm |
| 41 |
trying to accomplish this, and is there a better way to go about it?" |
| 42 |
If you're creating a ton of entries in /etc/portage you might be |
| 43 |
fighting the package manager more than necessary. There is nothing |
| 44 |
wrong with customizing things (that is basically what Gentoo is for), |
| 45 |
but you definitely need to learn how to manage that so that you don't |
| 46 |
make life hard on yourself. |
| 47 |
|
| 48 |
-- |
| 49 |
Rich |
Archives