From: Chong Lu <Chong.Lu@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-networking][PATCH 1/2] quagga: add subpkgs to RDEPENDS
Date: Mon, 29 Sep 2014 15:01:45 +0800 [thread overview]
Message-ID: <542903D9.8020104@windriver.com> (raw)
In-Reply-To: <1678777.vfoZ90ZxEi@sencha>
On 09/29/2014 01:51 PM, Roman Khimov wrote:
> В письме от 29 сентября 2014 09:19:52 пользователь Chong Lu написал:
>> +RDEPENDS_${PN} += "${PN}-babeld ${PN}-bgpd ${PN}-isisd ${PN}-ospf6d
>> ${PN}-ospfd ${PN}-ripd ${PN}-ripngd" +
> IMO the whole point of split daemon packaging was to be able to choose which
> protocols you want and which you don't. So forcing an RDEPENDS is wrong if you
> want to stay with per-daemon packages. I think RRECOMMENDS is better here.
OK. Thanks. I will resend a V2.
Best Regards
Chong
>
>
prev parent reply other threads:[~2014-09-29 7:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 1:19 [meta-networking][PATCH 1/2] quagga: add subpkgs to RDEPENDS Chong Lu
2014-09-29 1:19 ` [meta-networking][PATCH 2/2] quagga: add systemd service file Chong Lu
2014-09-29 5:51 ` [meta-networking][PATCH 1/2] quagga: add subpkgs to RDEPENDS Roman Khimov
2014-09-29 7:01 ` Chong Lu [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=542903D9.8020104@windriver.com \
--to=chong.lu@windriver.com \
--cc=openembedded-devel@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