[OE-core] [RFC v1 PATCH 00/16] populate perl-native into its own directory

[Richard Purdie]

On Wed, 2011-06-01 at 13:59 -0700, Tom Rini wrote:
> On 06/01/2011 01:45 PM, Phil Blundell wrote:
> > On Wed, 2011-06-01 at 13:42 -0700, Tom Rini wrote:
> >> What falls down in this case is that  once
> >> perl-native is built (and in our PATH), if it's a different version than
> >> system-wide perl, stuff starts failing on version mis-match.
> > 
> > I think that's the bit that I'm not properly understanding.  Which
> > versions are mismatching, exactly?  
> > 
> > Surely the local perl from the sysroot ought to be completely
> > self-contained and shouldn't be using any bits from the host perl
> > install at that point.
> 
> So this jogs my memory a bit!  It's not so much perl itself but stuff
> that uses perl that can get dirty and then no, you have stuff thats
> built for system perl and stuff that's built with perl-native clashing.
> 
> Relying even more on memory, I think help2man was one of the "easy"
> culprits and since we also modify the env, we do things like have
> help2man run with PERL5LIB and so on pointing system-wide perl at
> perl-native's lib directory and so forth.

But with the proposed patch series either:

a) help2man depends perlnative.bbclass

In this case it can depend on perl-native being there, its in path and
things work as per OE.dev.

b) help2man doesn't depend in perlnative.bbclass

It only sees the system perl.

So I'm still not clear where the problem is?

Cheers,

Richard