[oe] curious about "superfluous" meta-cpan recipes

[Robert P. J. Day]

On Tue, 15 Nov 2016, Jens Rehsack wrote:

> Hi Robert,
>
> > Am 14.11.2016 um 22:45 schrieb Robert P. J. Day <rpjday at crashcourse.ca>:
> >
> >
> >  to follow up on a point i made earlier, it seems that a number of
> > recipes in meta-cpan are, these days, unnecessary as they are
> > available in the standard OE or meta-oe layers. i took a quick
> > look and found the following examples:
> >
> > meta-cpan			OE/meta-oe equivalent		type
> >
> >
> > uri-perl			liburi-perl			oe-core
> > encode-locale-perl		libencode-locale-perl		meta-perl
> > io-socket-ssl-perl		libio-socket-ssl-perl		meta-perl

... snip ...

> >  so you can see that a number of meta-cpan recipes appear to be
> > effectively available in basic OE. does that make them
> > unnecessary? is there any reason to have meta-cpan recipes that
> > basically reproduce what is already available? (other than version
> > numbers, of course.)
>
> you're slightly too fast...

  that's what *she* said. :-) but seriously ...

> There is a clear reason for that what you identified as superfluous:
> reliability.
>
> Experienced users expected, one can easily add an
> liburi-perl_%.bbappend or an uri-perl_%.bbappend containing a
> PROVIDES+="...". But noone is enforced to remove such a PROVIDES...
>
> What drives me to package cpan distributions which are already in
> meta-oe? The way they're packaged. meta-cpan containes recipes in a
> way as they're meant by CPAN authors, not by Debian or
> oe-contributors.

  is there anywhere a guide for writing perl recipes? i've already
noticed the subtle differences in packaging, and someone earlier
mentioned to avoid the meta-debian recipes as they have their own
standard, and so on.

  is there a HOWTO for this? thanks muchly.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================