Alexander Kanavin

http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=akanavin/package-version-updates&id=000c5f50f9a0b7c287d36988243b1b2779fcd04f I'm splitting perl-cross into its own recipe, to ease updates and patch maintenance. That means it needs its own licensing info.

For reference, http://git.yoctoproject.org/cgit.cgi/poky-contrib/tree/meta/recipes-devtools/perl-cross/perlcross_1.3.6.bb?h=akanavin/package-version-updates is the recipe link that won't disappear on branch rebase.

'devtool upgrade' can't handle upgrading recipes which pull several tarballs from different locations, it would have to be significantly reengineered for what is a rather marginal use case. It's far...

I can for sure switch over to fetching from git, if you prefer not to have those files in the tarballs, no problem with that.

Sadly that won't work either. Those tarballs are auto-generated by github, and their checksums can, and do change spontaneously. Yocto specifically prohibits their use, and there's even an automated test...

No, there's no need to do that, the perl-cross recipe that I linked works perfectly. It unpacks and copies the content of the tarball into a sysroot ($sysroot/usr/share/perl-cross) for the...

I think we package configuration files for miniperl (native helper executable that is used in building target perl), which are specific for the host compiler and vary from one host...

Patch: http://lists.openembedded.org/pipermail/openembedded-core/2020-February/292501.html

make install is basically installing *.h, so maybe it's best to delete the file after the fact like my patch does. Also note that some headers, perl.h in particular actually...

Here: https://github.com/Perl/perl5/blob/blead/t/TEST#L479 The values of extensions and known_extensions are loaded from config.sh, then given to _tests_from_manifest() which expects them to be in the non-prefixed format.