On Wed, Aug 03, 2011 at 10:28:51PM +0100, Ciaran McCreesh wrote: > On Wed, 3 Aug 2011 14:26:56 -0700 > Brian Harring <ferri...@gmail.com> wrote: > > Aka, ebuild's should be written to assume the files they install get > > wiped; there is *zero* mention of mtime, nor could any ebuild rely on > > it and be compliant. > > But as it's a FEATURE, they can't assume that at all.
It's outside the ebuild's area of concern (think seperation of concerns), just the same as INSTALL_MASK. The ebuild, per spec, should be written to assume it's wiped. If the user overrides portages make.globals setting FEATURES=unmerge-orphans it is on the *users* head to maintain the fallout, just the same as if they go and set INSTALL_MASK to do something special. > So either we spec VDB and the unmerge process, which gets horrible for > all kinds of reasons, or ebuilds can't assume that things that have > been modified get wiped. This is getting more into "the sky is falling" territory. If you'd like to tighten the spec, go nuts, but there isn't anything to see here nor is there a real issue. This really is no different than INSTALL_MASK. ~brian
