1 |
On 12/17/2011 04:02 AM, Ciaran McCreesh wrote: |
2 |
> On Sat, 17 Dec 2011 10:47:47 +0000 |
3 |
> Markos Chandras <hwoarang@g.o> wrote: |
4 |
>> On 12/17/2011 08:32 AM, Ciaran McCreesh wrote: |
5 |
>>> On Fri, 16 Dec 2011 20:33:11 +0000 Markos Chandras |
6 |
>>> <hwoarang@g.o> wrote: |
7 |
>>>> to avoid useless compilations to slow machines |
8 |
>>> |
9 |
>>> That's a package manager issue, not an ebuild issue. |
10 |
>>> |
11 |
>> How come? The package appears to have a lower version compared to the |
12 |
>> previous one so the package manager treats it as a downgrade |
13 |
> |
14 |
> No, the issue that you think there's such a thing as a "useless |
15 |
> compilation". Your package manager should provide you with an easy way |
16 |
> of saying "I don't care about this package this time when I'm updating |
17 |
> world, so exclude it if possible". |
18 |
|
19 |
With emerge there are currently at least two possible ways to accomplish |
20 |
this: |
21 |
|
22 |
1) Put the package in /etc/portage/package.mask (it will trigger |
23 |
warnings about the installed package being masked though) |
24 |
|
25 |
2) Use the emerge --exclude option. |
26 |
|
27 |
If those don't fit well enough, we can add yet another way to do it. |
28 |
-- |
29 |
Thanks, |
30 |
Zac |