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