| 1 |
On 2010-04-18 11:54 AM, Arttu V. wrote: |
| 2 |
> On 4/18/10, Tanstaafl <tanstaafl@×××××××××××.org> wrote: |
| 3 |
>>>> You could try temporarily masking it: |
| 4 |
>>>> #echo sys-devel/gcc >> /etc/portage/package.mask |
| 5 |
>>>> |
| 6 |
>>>> Then updating: |
| 7 |
>>>> #emerge -e system |
| 8 |
>>>> |
| 9 |
>>>> Then removing the mask: |
| 10 |
>>>> #sed -i '$d' /etc/portage/package.mask |
| 11 |
>>>> |
| 12 |
>>>> I don't know of any emerge flag that does this in one step. |
| 13 |
>>> |
| 14 |
>>> Hmmm, good idea, thanks Vincent... |
| 15 |
>> |
| 16 |
>> Crap, doesn't look like this will work... |
| 17 |
> <snip/> |
| 18 |
>> |
| 19 |
>> Any other ideas? |
| 20 |
|
| 21 |
> A guess: try it with package.provided instead of package.mask. See the |
| 22 |
> section on portage man page. The syntax for package.provided requires |
| 23 |
> a full version atom (e.g., sys-devel/gcc-4.4.3-r1), but this approach |
| 24 |
> might not interfere with dep tree calculations like masking does. |
| 25 |
|
| 26 |
Noted for future reference as well Arttu, thanks... if it works I won't |
| 27 |
have to sit there and watch for the gcc compiles... |
| 28 |
|
| 29 |
-- |
| 30 |
|
| 31 |
Charles |
Archives