public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Joshua G Lock <joshua.g.lock@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH][fido][RESEND 4/5] texinfo: don't create dependency on INHERIT variable
Date: Fri, 15 Jan 2016 15:20:48 +0000	[thread overview]
Message-ID: <1452871248.16112.13.camel@linux.intel.com> (raw)
In-Reply-To: <20160115134144.GD2607@jama>

On Fri, 2016-01-15 at 14:41 +0100, Martin Jansa wrote:
> On Thu, Dec 10, 2015 at 02:48:20PM +0100, Martin Jansa wrote:
> > * we don't want the do_package signature depending on INHERIT
> > variable
> > * e.g. just adding the own-mirrors causes texinfo to rebuild:
> >   # bitbake-diffsigs BUILD/sstate-diff/*/*/texinfo/*do_package.sig*
> >   basehash changed from 015df2fd8e396cc1e15622dbac843301 to
> > 9f1d06c4f238c70a99ccb6d8da348b6a
> >   Variable INHERIT value changed from
> >   ' rm_work blacklist blacklist report-error ${PACKAGE_CLASSES}
> > ${USER_CLASSES} ${INHERIT_DISTRO} ${INHERIT_BLACKLIST} sanity'
> >   to
> >   ' rm_work own-mirrors blacklist blacklist report-error
> > ${PACKAGE_CLASSES} ${USER_CLASSES} ${INHERIT_DISTRO}
> > ${INHERIT_BLACKLIST} sanity'
> 
> Joshua,
> 
> why this one didn't make it to your fido update?

(For the benefit of the list and with apologies to Martin for the spam)

Apologies, that wasn't an intentional omission. I've pushed it to my
joshuagl/fido-next branch and will include it in the next merge request
(hopefully today).

Regards,

Joshua


  reply	other threads:[~2016-01-15 15:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-10 13:48 [PATCH][fido][RESEND 0/5] Backports for fido Martin Jansa
2015-12-10 13:48 ` [PATCH][fido][RESEND 1/5] layer.conf: Add several allarch dependency exclusions Martin Jansa
2015-12-10 13:48 ` [PATCH][fido][RESEND 2/5] layer.conf: Add missing dependency for allarch package initramfs-framework Martin Jansa
2015-12-10 13:48 ` [PATCH][fido][RESEND 3/5] allarch: Force TARGET_*FLAGS variable values Martin Jansa
2015-12-10 13:48 ` [PATCH][fido][RESEND 4/5] texinfo: don't create dependency on INHERIT variable Martin Jansa
2016-01-15 13:41   ` Martin Jansa
2016-01-15 15:20     ` Joshua G Lock [this message]
2015-12-10 13:48 ` [PATCH][fido][RESEND 5/5] linux-dtb.inc: drop unused DTB_NAME variable from do_install Martin Jansa
2015-12-10 14:58 ` [PATCH][fido] feature-arm-thumb.inc: Fix ARMPKGSFX_THUMB value Martin Jansa
2015-12-16 20:57 ` [PATCH][fido][RESEND 0/5] Backports for fido Joshua Lock
2016-01-15 12:06 ` Martin Jansa

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=1452871248.16112.13.camel@linux.intel.com \
    --to=joshua.g.lock@linux.intel.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