All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: joshua.g.lock@intel.com, 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 14:41:44 +0100	[thread overview]
Message-ID: <20160115134144.GD2607@jama> (raw)
In-Reply-To: <7e6b70331d609496c4e21884682c2e93af0347a7.1449754339.git.Martin.Jansa@gmail.com>

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

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?

> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
>  meta/recipes-extended/texinfo/texinfo_5.2.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-extended/texinfo/texinfo_5.2.bb b/meta/recipes-extended/texinfo/texinfo_5.2.bb
> index 8dbcaa1..c9ac182 100644
> --- a/meta/recipes-extended/texinfo/texinfo_5.2.bb
> +++ b/meta/recipes-extended/texinfo/texinfo_5.2.bb
> @@ -10,7 +10,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504"
>  PROVIDES_append_class-native = " texinfo-replacement-native"
>  
>  def compress_pkg(d):
> -    if "compress_doc" in (d.getVar("INHERIT", True) or "").split():
> +    if bb.data.inherits_class('compress_doc', d):
>           compress = d.getVar("DOC_COMPRESS", True)
>           if compress == "gz":
>               return "gzip"
> -- 
> 2.6.3
> 

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

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

  reply	other threads:[~2016-01-15 13:40 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 [this message]
2016-01-15 15:20     ` Joshua G Lock
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=20160115134144.GD2607@jama \
    --to=martin.jansa@gmail.com \
    --cc=joshua.g.lock@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 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.