Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Joe MacDonald <Joe_MacDonald@mentor.com>
To: akuster808 <akuster808@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking][PATCH 1/2] proftpd: fix rdepends issue
Date: Tue, 6 Jan 2015 23:36:01 -0500	[thread overview]
Message-ID: <20150107043600.GD10013@mentor.com> (raw)
In-Reply-To: <54AC9065.70108@gmail.com>

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

[Re: [oe] [meta-networking][PATCH 1/2] proftpd: fix rdepends  issue] On 15.01.06 (Tue 17:48) akuster808 wrote:

> 
> 
> On 01/06/2015 08:26 AM, Martin Jansa wrote:
> >On Tue, Jan 06, 2015 at 07:59:19AM -0800, Armin Kuster wrote:
> >>Signed-off-by: Armin Kuster <akuster808@gmail.com>
> >>---
> >>  meta-networking/recipes-daemons/proftpd/proftpd_1.3.5.bb | 2 +-
> >>  1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >>diff --git a/meta-networking/recipes-daemons/proftpd/proftpd_1.3.5.bb b/meta-networking/recipes-daemons/proftpd/proftpd_1.3.5.bb
> >>index cba39e8..7d285a0 100644
> >>--- a/meta-networking/recipes-daemons/proftpd/proftpd_1.3.5.bb
> >>+++ b/meta-networking/recipes-daemons/proftpd/proftpd_1.3.5.bb
> >>@@ -99,4 +99,4 @@ USERADD_PARAM_${PN} = "--system -g ${FTPGROUP} --home-dir /var/lib/${FTPUSER} --
> >>
> >>  FILES_${PN} += "/home/${FTPUSER}"
> >>
> >>-RDEPENDS_${PN} += "perl"
> >>+RDEPENDS_${PN} += "perl initscripts-functions"
> >
> >It's not that simple.
> 
> Had to try :)
> >
> >The initscripts-functions is added to RDEPENDS conditionally based on
> >"sysvinit" in DISTRO_FEATURES and INHIBIT_UPDATERCD_BBCLASS.
> >
> >Adding it explicitly here will pull it to image even for people who
> >care only about systemd services (and don't want any iniscripts to
> >pollute their startup sequence).
> 
> make sense.
> 
> >
> >See meta/classes/update-rc.d.bbclass
> 
> thanks for the reference.
> >
> >I know we already have one recipe like this:
> >meta-oe/recipes-connectivity/krb5/krb5_1.12.2.bb:RDEPENDS_${PN} += "initscripts-functions"
> >
> >but honestly silencing this warning like this does more harm then
> >the warning. I think it should be fixed in bbclass, because all
> >recipes which inherit it, suffer from this. Maybe by adding another
> >VIRTUAL_RUNTIME which can be set to empty when sysv isn't enabled.
> 
> k.
> 
> Does the 5 second rule count ? or because I touched it I am stuck
> with it ; )

If you invoke the five-second-rule, I think it can apply, but if you're
anything like me, once you step in something it's almost impossible to
pretend you didn't.  ;-)

-J.

> 
> I will take a look.
> 
> thanks,
> Armin
> >
> >
> >
-- 
-Joe MacDonald.
:wq

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

  reply	other threads:[~2015-01-07  4:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 15:59 [meta-networking][PATCH 0/2] world build fixes Armin Kuster
2015-01-06 15:59 ` [meta-networking][PATCH 1/2] proftpd: fix rdepends issue Armin Kuster
2015-01-06 16:26   ` Martin Jansa
2015-01-06 16:33     ` Paul Eggleton
2015-01-07  1:48     ` akuster808
2015-01-07  4:36       ` Joe MacDonald [this message]
2015-01-06 15:59 ` [meta-networking][PATCH 2/2] netkit-rwho: " Armin Kuster

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=20150107043600.GD10013@mentor.com \
    --to=joe_macdonald@mentor.com \
    --cc=akuster808@gmail.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