From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 01/12] nss: update to 3.21
Date: Thu, 21 Jan 2016 16:50:19 +0200 [thread overview]
Message-ID: <56A0F02B.9000600@linux.intel.com> (raw)
In-Reply-To: <D70F5507-7ED6-4281-8FC9-4BFE9EAD0B72@gmail.com>
On 01/19/2016 09:05 PM, Khem Raj wrote:
>> + export NSS_DISABLE_GTESTS=1
>> +
>
> this export is appearing twice
> can it be optimized ?
I'm only following the pattern in the nss recipe: it has custom
do_compile() and do_install() sections which to a large extend duplicate
each other. Eliminating this duplication was not a goal, I just wanted
to update to latest upstream.
Alex
next prev parent reply other threads:[~2016-01-21 14:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 15:37 [PATCH 00/12] Package version updates and version check fixes Alexander Kanavin
2016-01-19 15:37 ` [PATCH 01/12] nss: update to 3.21 Alexander Kanavin
2016-01-19 19:05 ` Khem Raj
2016-01-21 14:50 ` Alexander Kanavin [this message]
2016-01-21 15:18 ` Khem Raj
2016-01-19 15:37 ` [PATCH 02/12] bootchart2: update to 0.14.8 Alexander Kanavin
2016-01-19 15:37 ` [PATCH 03/12] btrfs-tools: update to 4.4 Alexander Kanavin
2016-01-19 15:37 ` [PATCH 04/12] build-appliance-image: bump version to 14.0 Alexander Kanavin
2016-01-19 15:37 ` [PATCH 05/12] e2fsprogs: fix upstream version check Alexander Kanavin
2016-01-19 15:37 ` [PATCH 06/12] libsolv: " Alexander Kanavin
2016-01-19 15:37 ` [PATCH 07/12] ncurses: " Alexander Kanavin
2016-01-19 15:37 ` [PATCH 08/12] pbzip2: update to 1.1.13 Alexander Kanavin
2016-01-19 15:37 ` [PATCH 09/12] sysstat: fix upstream version check Alexander Kanavin
2016-01-19 15:37 ` [PATCH 10/12] gnutls: update to 3.4.8 Alexander Kanavin
2016-01-19 15:37 ` [PATCH 11/12] libical: fix upstream version check Alexander Kanavin
2016-01-19 15:37 ` [PATCH 12/12] libjpeg-turbo: fix upstream version check (sort of) Alexander Kanavin
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=56A0F02B.9000600@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox