1 |
There should not be a collision of the dropin.cache in the first place. |
2 |
|
3 |
By adding the cache files to COLLISION_IGNORE it will just hide the |
4 |
collision problem and create other one (with obsolette caches), harder |
5 |
to debug. |
6 |
|
7 |
On Sat, 10 Aug 2013 11:19:59 +0200 |
8 |
Michał Górny <mgorny@g.o> wrote: |
9 |
|
10 |
> Dnia 2013-08-09, o godz. 11:32:12 |
11 |
> Michał Górny <mgorny@g.o> napisał(a): |
12 |
> |
13 |
> > Hello, |
14 |
> > |
15 |
> > Just a quick one. |
16 |
> > |
17 |
> > Currently, the two listed variables are set in make.globals |
18 |
> > (installed by portage ebuild); |
19 |
> > |
20 |
> > COLLISION_IGNORE="/lib/modules/* *.py[co] *\$py.class" |
21 |
> > UNINSTALL_IGNORE="/lib/modules/*" |
22 |
> |
23 |
> I've committed the following values for now: |
24 |
> |
25 |
> COLLISION_IGNORE="/lib/modules/* *.py[co] *\$py.class */dropin.cache" |
26 |
> UNINSTALL_IGNORE="/lib/modules/*" |
27 |
> |
28 |
> We can discuss further changes without users suffering. |
29 |
> |