| 1 |
Arttu V. wrote: |
| 2 |
> On 1/22/10, Arnau Bria <arnau@×××××××××.net> wrote: |
| 3 |
> |
| 4 |
>> Hi all, |
| 5 |
>> |
| 6 |
>> I'm wondering which is the correct way for unmasking several |
| 7 |
>> depending packages when you want to unmask only want. |
| 8 |
>> |
| 9 |
>> Let me explain, I want to unmask xorg-server, and every time I try to |
| 10 |
>> update, it complains about one package, I unmask it, then it complains |
| 11 |
>> about other, and so on... |
| 12 |
>> |
| 13 |
>> so, is there a good/correct way for doing so? |
| 14 |
>> |
| 15 |
> |
| 16 |
> You might want to try and emerge autounmask: |
| 17 |
> |
| 18 |
> http://www.iml.ece.mcgill.ca/~stephan/autounmask |
| 19 |
> |
| 20 |
> It's not necessarily the "right" way, and I don't use it, but |
| 21 |
> apparently some (many?) do. |
| 22 |
> |
| 23 |
> |
| 24 |
|
| 25 |
I use it here for some of the bigger things like KDE. It works well. |
| 26 |
|
| 27 |
Also, if you have a directory for /etc/portage/package.* as I do, it |
| 28 |
will create a new file when you run it. To undo the unmask, just remove |
| 29 |
or delete the file. If you still have package.* files, it uses a |
| 30 |
separator so you know what it added. You can delete that section if you |
| 31 |
want to go back. |
| 32 |
|
| 33 |
You may also want to check out the option with autounmask. I use the -n |
| 34 |
option sometimes. |
| 35 |
|
| 36 |
Dale |
| 37 |
|
| 38 |
:-) :-) |
Archives