From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Kang Kai <Kai.Kang@windriver.com>
Cc: Zhenfeng.Zhao@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] nativesdk-autoconf: add dependencies
Date: Mon, 22 Oct 2012 11:47:13 +0100 [thread overview]
Message-ID: <1350902833.2520.71.camel@ted> (raw)
In-Reply-To: <50851CC4.6040501@windriver.com>
On Mon, 2012-10-22 at 18:15 +0800, Kang Kai wrote:
> Hi Richard,
>
> > a) Decide whether the sdk should be using the nativesdk perl or the host
> > system one. I'm fine with deciding we should use the nativesdk perl
> > b) Fix RDEPENDS_${PN} for autoconf so that it lists the right perl
> > modules.
>
> I have put every single perl module to autoconf's rdepend. I also update
> the dependencies among perl modules themselves.
Does autoconf need every single perl module? We should only add
dependencies for the perl modules it needs.
> > c) At this pooint we might be able to simply remove RDEPENDS_
> > ${PN}_virtclass-nativesdk and the code should figure things out
> > automagically itself.
>
> It looks fine when remove the RDEPENDS_ ${PN}_virtclass-nativesdk from
> autoconf.
Great!
> > d) We should verify the list of modules for automake is correct
>
> Because automake depends on autoconf, so how about I remove the
> perl-module-* in automake's rdepends these already in autoconf rdepends?
If there is already a dependency there, this sounds fine.
> > e) We should also see if we can simply remove the RDEPENDS_
> > ${PN}_virtclass-nativesdk line from automake.
>
> I'll try to remove it.
Cheers,
Richard
prev parent reply other threads:[~2012-10-22 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 11:22 [PATCH 0/2] Fix (nativesdk-)perl dependency issues Kang Kai
2012-10-19 11:22 ` [PATCH 1/2] perl: fix dependecies Kang Kai
2012-10-19 11:22 ` [PATCH 2/2] nativesdk-autoconf: add dependencies Kang Kai
2012-10-19 15:01 ` Richard Purdie
2012-10-22 10:15 ` Kang Kai
2012-10-22 10:47 ` Richard Purdie [this message]
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=1350902833.2520.71.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=Kai.Kang@windriver.com \
--cc=Zhenfeng.Zhao@windriver.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