From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>,
"Eggleton, Paul" <paul.eggleton@intel.com>
Subject: Re: lib/oe/sstatesig: Ensure packagegroups don't continually rebuild
Date: Thu, 07 Nov 2013 22:57:10 +0000 [thread overview]
Message-ID: <1383865030.6271.283.camel@ted> (raw)
In-Reply-To: <CAP9ODKrQ9aEx8VH8qhjuBORaDyGp72a3BXsHTkRosqB53zGOTg@mail.gmail.com>
On Thu, 2013-11-07 at 13:58 -0200, Otavio Salvador wrote:
> On Wed, Nov 6, 2013 at 9:42 PM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > On Wed, 2013-11-06 at 16:51 -0200, Otavio Salvador wrote:
> >> On Tue, Nov 5, 2013 at 8:15 PM, Richard Purdie
> >> <richard.purdie@linuxfoundation.org> wrote:
> >> > packagegroups are allarch and shouldn't change depending on the target
> >> > or machine selected. In general they should have good stable namespaces
> >> > for their dependencies. As such we can exclude them from rebuilding when
> >> > dependency checksums change.
> >> >
> >> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> >>
> >> What about machine-base and core-boot? this may change depending on machine.
> >
> > Those already get marked as machine specific. I'd not expect
> > dependencies to be changing package names there for example so I'm not
> > sure this is an issue.
>
> In:
>
> + def isPackageGroup(fn):
> + inherits = " ".join(dataCache.inherits[fn])
> + return "packagegroup.bbclass" in inherits
>
> We must check PACKAGE_ARCH, no?
No. The fact they're marked as MACHINE_ARCH ensures they change when
they need to, we don't need sstate to do that as well.
Cheers,
Richard
next prev parent reply other threads:[~2013-11-07 22:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 22:15 lib/oe/sstatesig: Ensure packagegroups don't continually rebuild Richard Purdie
2013-11-06 18:51 ` Otavio Salvador
2013-11-06 23:42 ` Richard Purdie
2013-11-07 15:58 ` Otavio Salvador
2013-11-07 22:57 ` Richard Purdie [this message]
2013-11-08 11:55 ` Otavio Salvador
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=1383865030.6271.283.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=paul.eggleton@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.