No. It will make the migration to owned caches simpler while keeping track of them.
> By adding the cache files to COLLISION_IGNORE it will just hide the > collision problem and create other one (with obsolette caches), harder > to debug. Yep, that's why I have submitted a patch to portage that prevents applying COLLISION_IGNORE to owned files. > There should not be a collision of the dropin.cache in the first place. First of all, please reply below mails as otherwise reading them is difficult. Dnia 2013-08-12, o godz. 13:46:16 yac <y...@gentoo.org> napisał(a): > On Sat, 10 Aug 2013 11:19:59 +0200 > Michał Górny <mgo...@gentoo.org> wrote: > > > Dnia 2013-08-09, o godz. 11:32:12 > > Michał Górny <mgo...@gentoo.org> napisał(a): > > > > > Hello, > > > > > > Just a quick one. > > > > > > Currently, the two listed variables are set in make.globals > > > (installed by portage ebuild); > > > > > > COLLISION_IGNORE="/lib/modules/* *.py[co] *\$py.class" > > > UNINSTALL_IGNORE="/lib/modules/*" > > > > I've committed the following values for now: > > > > COLLISION_IGNORE="/lib/modules/* *.py[co] *\$py.class */dropin.cache" > > UNINSTALL_IGNORE="/lib/modules/*" > > > > We can discuss further changes without users suffering. > > > -- Best regards, Michał Górny
signature.asc
Description: PGP signature
