Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Sergey 'Jin' Bostandzhyan <jin@mediatomb.cc>
To: Christopher Larson <clarson@kergoth.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Problem with RDEPENDS in multimachine builds for allarch packages
Date: Mon, 26 Oct 2015 17:26:50 +0100	[thread overview]
Message-ID: <20151026162650.GA16758@deadlock.dhs.org> (raw)
In-Reply-To: <CABcZANn=aL5i2UOVF-p69yBCB2xv_Sn0G_82NetvQa4WXCiKtg@mail.gmail.com>

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.

Kind regards,
Sergey



  reply	other threads:[~2015-10-26 16:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-26 15:13 Problem with RDEPENDS in multimachine builds for allarch packages Sergey 'Jin' Bostandzhyan
2015-10-26 16:13 ` Christopher Larson
2015-10-26 16:26   ` Sergey 'Jin' Bostandzhyan [this message]
2015-10-26 18:20     ` Martin Jansa
2015-10-27  8:30 ` Mike Looijmans
2015-10-27  8:36   ` Richard Purdie
2015-10-27  8:58     ` Mike Looijmans

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151026162650.GA16758@deadlock.dhs.org \
    --to=jin@mediatomb.cc \
    --cc=clarson@kergoth.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox