Another idea could be to append the perl version and arch string to the source code before calculating the MD5 signature that is used to decide if we must rebuild or not. That way a change or perl and/or arch would automatically trigger a rebuild.
Not sure if this has any other impacts, but I thought I'd just throw the idea out there... Patrick On 11/6/08, Sisyphus <[EMAIL PROTECTED]> wrote: > > ----- Original Message ----- > From: "Erik Hollensbe" <[EMAIL PROTECTED]> > To: <inline@perl.org> > . > . >> >> 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. > > Good point ... I'll investigate that. If it can be implemented (and I expect > it can), it's probably a better approach than my proposal. > > Cheers, > Rob > > -- Sent from my mobile device ===================== Patrick LeBoutillier Rosemère, Québec, Canada
