| 1 |
Alan McKinnon wrote: |
| 2 |
> On Sunday 05 October 2008 20:16:55 Neil Bothwick wrote: |
| 3 |
> |
| 4 |
>> On Sun, 05 Oct 2008 20:08:23 +0200, b.n. wrote: |
| 5 |
>> |
| 6 |
>>> Could you share your relevant package.mask and package.keywords, for |
| 7 |
>>> the laziest of us? :) |
| 8 |
>>> |
| 9 |
>> emerge autounmask |
| 10 |
>> autounmask kde-meta |
| 11 |
>> |
| 12 |
> |
| 13 |
> For the super-lazy amongst us, what does that package do? |
| 14 |
> |
| 15 |
> OK, I can figure out what it does, so my real question should be "what other |
| 16 |
> stuff does it do that I might not expect? Any gotchas?" |
| 17 |
> |
| 18 |
> I've become ... wary ... of useful sounding packages that claim to automate |
| 19 |
> tricky portage things |
| 20 |
> |
| 21 |
> |
| 22 |
> |
| 23 |
|
| 24 |
I have used it and it seems to work pretty good. I must confess that I |
| 25 |
backed up my /etc just in case. ;-) Never hurts right? |
| 26 |
|
| 27 |
I used it to unmask KDE 4 when it first came out just to see what, if |
| 28 |
anything, was different. Since I am still on dial-up and KDE 4 was |
| 29 |
updating a pretty good bit, I went back to KDE 3.5. |
| 30 |
|
| 31 |
I also like the way it separated what it added to the package.* files |
| 32 |
from what I already had there. In Kwrite for example, you can just |
| 33 |
highlight from where it started to the end, hit delete and it is like it |
| 34 |
never happened. |
| 35 |
|
| 36 |
May be worth a try, just back up /etc first. Just in case your mileage |
| 37 |
varies. :-p |
| 38 |
|
| 39 |
Dale |
| 40 |
|
| 41 |
:-) :-) |
Archives