From: Saul Wold <sgw@linux.intel.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 16/17] cmake: Update to 2.8.10.1
Date: Mon, 19 Nov 2012 10:12:28 -0800 [thread overview]
Message-ID: <50AA768C.3030503@linux.intel.com> (raw)
In-Reply-To: <CAP9ODKqqud-1kvFVWqgoe_CJgyro4=eBSNfV_g02FP77EAvFWA@mail.gmail.com>
On 11/19/2012 02:20 AM, Otavio Salvador wrote:
>
>
> On Mon, Nov 19, 2012 at 3:54 AM, Saul Wold <sgw@linux.intel.com
> <mailto:sgw@linux.intel.com>> wrote:
>
> Rebase the patches due to macro name changes.
>
> Signed-off-by: Saul Wold <sgw@linux.intel.com
> <mailto:sgw@linux.intel.com>>
> ...
>
> -PR = "${INC_PR}.0"
> -
> -SRC_URI[md5sum] = "ba74b22c788a0c8547976b880cd02b17"
> -SRC_URI[sha256sum] =
> "2b59897864d6220ff20aa8eac64cac8994e004898a1c0f899c8cb4d7b7570b46"
>
>
> I find it hard to spot the checksums to be in the .inc file.
>
> I'd prefer to have them in the .bb recipes (even if in this case it'd be
> a duplication).
>
I am not sure why this is an issue, we already have about a dozen places
where the SRC_URI and checksum info is located in the .inc file.
> In case you would like to avoid the duplication (which I agree) you
> might before, or later, merge the native handle onto the cmake_<ver>.bb
> recipe.
>
> What do you think?
>
Looks like there are bigger issues with trying to merge native into the
standard recipe, mostly due to the fact that the target recipe inherits
cmake, while the native version does not.
Sau!
> --
> Otavio Salvador O.S. Systems
> E-mail: otavio@ossystems.com.br <mailto:otavio@ossystems.com.br>
> http://www.ossystems.com.br
> Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
>
next prev parent reply other threads:[~2012-11-19 18:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 5:54 [PATCH 00/17] Recipe Updates Saul Wold
2012-11-19 5:54 ` [PATCH 01/17] sysstat: Update to 10.1.2 Saul Wold
2012-11-19 5:54 ` [PATCH 02/17] libcheck: Update to 0.9.9 Saul Wold
2012-11-19 5:54 ` [PATCH 03/17] sqlite3: Update to 3.7.14.1 Saul Wold
2012-11-19 5:54 ` [PATCH 04/17] builder: Add password for user Saul Wold
2012-11-19 5:54 ` [PATCH 05/17] libtasn1: Update to 2.14 Saul Wold
2012-11-19 5:54 ` [PATCH 06/17] gnutls: Update to 2.12.21 Saul Wold
2012-11-19 5:54 ` [PATCH 07/17] libksba: Update to 1.3.0 Saul Wold
2012-11-19 5:54 ` [PATCH 08/17] dhcp: Update to 4.2.4-P2 Saul Wold
2012-11-19 5:54 ` [PATCH 09/17] libxml2: Update to 2.9.0 Saul Wold
2012-11-19 5:54 ` [PATCH 10/17] resolvconf: Update to 1.68 Saul Wold
2012-11-19 5:54 ` [PATCH 11/17] mc: Update to 4.8.6 Saul Wold
2012-11-19 5:54 ` [PATCH 12/17] man-pages: Update to 3.44 Saul Wold
2012-11-19 5:54 ` [PATCH 13/17] tiff: Update to 4.0.3 Saul Wold
2012-11-19 5:54 ` [PATCH 14/17] rt-tests/hwlatdetect: Update to 0.84 Saul Wold
2012-11-19 10:26 ` Otavio Salvador
2012-11-19 5:54 ` [PATCH 15/17] libdumpvalue-perl: Update to 1.17 Saul Wold
2012-11-19 5:54 ` [PATCH 16/17] cmake: Update to 2.8.10.1 Saul Wold
2012-11-19 10:20 ` Otavio Salvador
2012-11-19 18:12 ` Saul Wold [this message]
2012-11-19 18:34 ` Otavio Salvador
2012-11-19 5:54 ` [PATCH 17/17] libproxy: set LIBEXEC_INSTALL_DIR Saul Wold
2012-11-19 10:29 ` Otavio Salvador
2012-11-19 10:31 ` [PATCH 00/17] Recipe Updates 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=50AA768C.3030503@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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