[yocto] allarch class used in autoconf-archive recipe

[Dudziak Krzysztof]

Hi,
myself grabbed autoconf-archive recipe from
http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-devtools/autoconf-archive/autoconf-archive_2018.03.13.bb
to build and install autoconf archive for building user-space app. autoconf-archive package builds in Jethro,
as the YP release used here is, without problems even if grabbed from release later than Jethro.
That recipe inherits 'allarch' class.

If to review Jethro Reference Manual following note can be found reg. 'allarch' class usage:

"Unlike some distro recipes (e.g. Debian), OpenEmbedded recipes that produce packages that depend on tunings
through use of the RDEPENDS and TUNE_PKGARCH variables, should never be configured for all architectures using allarch.
This is the case even if the recipes do not produce architecture-specific output.

Configuring such recipes for all architectures causes the do_package_write_* tasks to have different signatures
for the machines with different tunings. Additionally, unnecessary rebuilds occur every time
an image for a different MACHINE is built even when the recipe never changes."

Same note is to be found on reference manual's master branch.

Few questions arise from that:
1. What might be best solution to the discrepancy "not recommended to use vs. used in OE-recipe"; to drop this inheritance?
2. How might recipe's past change-flow resulting in recipe's current version to inherit 'allarch' class look like?
________________________________
This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20180912/f80f6420/attachment.html>