List Archive: gentoo-council
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
>>>>> On Sun, 6 Dec 2009, David Leverton wrote:
> The intention is to make the spec for a new EAPI unnecessarily
> complex, just to avoid changing an existing implementation?
The spec first proposed was along the lines "mtime is updated if
(and only if) the package manager modifies the file" , but the
Paludis party raised objections that this was not specific enough.
But see below about "common sense".
>> We should also consider including this in EAPI 0 retroactively
> Doing things like that defeats the purpose of EAPI.
Normally I would agree with this. However, in this particular case the
damage has already been done. We wouldn't break anything by applying
this retroactively. The breakage of packages will go away in the
moment when all package managers preserve mtimes, independent of what
we write into the spec. So we could as well keep it simple (i.e.
without distinction between EAPIs).
> People are expected to use common-sense when reading it (since we
> don't have enough man-power to make it completely airtight), [...]
I fully agree. If such wisdom had been used earlier, the whole issue
would long be off the stove.