In order for the dpkg perl modules to be used the must reside in the
versioned perl library directory (as to be in the default include path).
Be explicit about this location in our FILES_${PN}-perl directive, so
that if this breaks in the future, the recipe will fail). We can now
drop the custom d
On 9 June 2017 at 01:00, Tom Rini wrote:
> In order for the dpkg perl modules to be used the must reside in the
> versioned perl library directory (as to be in the default include path).
> Be explicit about this location in our FILES_${PN}-perl directive, so
> that if this breaks in the future, t
On Fri, Jun 09, 2017 at 05:15:07PM +0100, Burton, Ross wrote:
> On 9 June 2017 at 01:00, Tom Rini wrote:
>
> > In order for the dpkg perl modules to be used the must reside in the
> > versioned perl library directory (as to be in the default include path).
> > Be explicit about this location in o
On Fri, Jun 09, 2017 at 05:15:07PM +0100, Burton, Ross wrote:
> On 9 June 2017 at 01:00, Tom Rini wrote:
>
> > In order for the dpkg perl modules to be used the must reside in the
> > versioned perl library directory (as to be in the default include path).
> > Be explicit about this location in o
On Fri, Jun 09, 2017 at 03:28:40PM -0400, Tom Rini wrote:
> On Fri, Jun 09, 2017 at 05:15:07PM +0100, Burton, Ross wrote:
> > On 9 June 2017 at 01:00, Tom Rini wrote:
> >
> > > In order for the dpkg perl modules to be used the must reside in the
> > > versioned perl library directory (as to be in
