On Wednesday 05 November 2008 01:37:41 Sisyphus wrote:
> Should this be implemented ?
> It's to be noted that the "DIRECTORY" Inline config option already provides
> the means for the user to attend to this problem himself, without any need
> to alter Inline at all. (I've detailed how that can be done in my reply to
> the bug report.)
Would just recording this information in the _Inline directory be sufficient?
I'm thinking of a situation where someone upgrades perl, and a ton of these
directories are still lying around; I would think the preferable situation
would be to create as few generated files as possible.
Under this assumption, the logic would look something like this:
if _Inline exists:
check stub version indicator against perl build/version
if equal, execute
otherwise, rebuild
otherwise
rebuild
This seems simple and straightforward, and users only face a
performance/maintenance penalty when they alternate versions of perl (which
may happen a lot or a little, depending on what their task is), and in the
worst case (say, on a CPAN test smoker box), they can still control it in the
environment and have a consistent build.
-Erik
