Re: Problem with RDEPENDS in multimachine builds for allarch packages

[Martin Jansa <martin.jansa@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1498 bytes --]

On Mon, Oct 26, 2015 at 05:26:50PM +0100, Sergey 'Jin' Bostandzhyan wrote:
> On Mon, Oct 26, 2015 at 09:13:22AM -0700, Christopher Larson wrote:
> > Afaik the most likely cause is your rdepends isn't allarch, so is being rebuilt
> > for the new machine, which causes yours to be rebuilt since it depends on it.
> 
> So, that means that anything arch specific listed in RDEPENDS will
> always cause the package to rebuild even if there were no changes in the
> package itself nor in the RDEPENDS packages? Is this really the desired
> behaviour?
> 
> I'd expect that if nothing has changed, nothing should get rebuild.. I
> often saw a huge number of packages being rebuilt and could never
> explain why this was happening, now it's becoming clear that probably
> some of them had some RDEPENDS set.
> 
> If you say it's not a bug - ok, now I at least know what's happening.
> Still, imho it would be nice and it would speed up things if only stuff
> that has really changed or stuff that depends on other things that have 
> really changed gets triggered.

You can use
openembedded-core/scripts/sstate-diff-machines.sh
to compare the signatures. It's also useful to store the output
directories in case you see some unexpected rebuilds in some future
build.

This script is used to generate reports like this one:
http://lists.openembedded.org/pipermail/openembedded-core/2015-October/111554.html

Regards,
-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]