On Wed, Oct 22, 2008 at 09:54:45PM +0200, Slaven Rezic wrote:
> Aristotle Pagaltzis <[EMAIL PROTECTED]> writes:
> > * David Cantrell <[EMAIL PROTECTED]> [2008-10-22 16:55]:
> > > There's two potential problems here. The first is that I'd
> > > already tested something else Inline-ish in that testing run,
> > > which hadn't cleared up properly after itself.
> > Presumably this could happen in realworld scenarios where a user
> > is installing something with multiple Inline::* dependencies, no?
> > If so, isn?t it a problem that needs to be fixed rather than
> > masked?
> Like this bug report?
> http://rt.cpan.org/Ticket/Display.html?id=29326
That's arguably a bug in Inline itself, not in modules that depend on
it. Now that we know that Inline has this bug, and it has been reported
to the author, it makes sense to do what we can to mitigate it when
testing other peoples' code. Setting the env var appropriately so that
different builds of perl get different Inline caches does that.
It won't guard against *all* potential Inline problems of course.
--
David Cantrell | Nth greatest programmer in the world
Good advice is always certain to be ignored,
but that's no reason not to give it -- Agatha Christie
