(apparently, i am doomed to poke around in OE perl recipes for the
next little while. le *sigh* ...)
curious about the following under meta-openembedded/meta-perl:
$ grep -r RPROVIDES *
recipes-perl/libtest/libtest-harness-perl_3.36.bb:RPROVIDES_${PN} +=
"libapp-prove-perl \
recipes-perl/libio/libio-stringy-perl_2.111.bb:RPROVIDES_${PN} += "
libio-atomicfile-perl \
recipes-perl/libmoo/libmoo-perl_2.000002.bb:RPROVIDES_${PN} = "
libmethod-inliner-perl \
recipes-perl/libextutils/libextutils-parsexs-perl_3.24.bb:RPROVIDES_${PN} += "
libextutils-parsexs-constants-perl \
recipes-perl/libencode/libencode-perl_2.83.bb:RPROVIDES_${PN} +=
"libencode-alias-perl \
recipes-perl/libhtml/libhtml-tree-perl_5.03.bb:RPROVIDES_${PN} = "
libhtml-element-perl \
recipes-perl/librole/librole-tiny-perl_2.000001.bb:RPROVIDES_${PN} = "
librole-tiny-perl \
recipes-perl/libcgi/libcgi-perl_4.28.bb:RPROVIDES_${PN} += "perl-module-cgi"
$
it's that last line that's odd ... i thought the naming convention
was that the "perl-module-" prefix was reserved for modules generated
by the base build of perl itself, while independent recipes used names
with prefixes of "libxxx-yyyy-perl" and, therefore, provided, well,
exactly that.
so what's the rationale for the RPROVIDES in that last example?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
--
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
