From: Martin Jansa <martin.jansa@gmail.com>
To: "David Nyström" <david.c.nystrom@gmail.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [RFC][PATCH] udev: add udev-utils to RDEPENDS
Date: Mon, 3 Feb 2014 15:19:26 +0100 [thread overview]
Message-ID: <20140203141914.GB3698@jama> (raw)
In-Reply-To: <52EF97D6.8090708@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1840 bytes --]
On Mon, Feb 03, 2014 at 02:21:26PM +0100, David Nyström wrote:
> On mån 3 feb 2014 14:03:47, Paul Eggleton wrote:
> > Hi David,
> >
> > On Monday 03 February 2014 13:58:49 David Nyström wrote:
> >> An intended fix for below error message with core-image-lsb,
> >> Sending this as an RFC since I dont really know what constitutes
> >> a RRECOMMENDS vs. RDEPENDS.
> >> Is this clearly defined somewhere ?
> >> Below should be an RDEPENDS, no ?
> >
> > Does this actually fix the problem though? An RRECOMMENDS would only not be
> > satisfied if the package ended up empty, or you were using BAD_RECOMMENDATIONS
> > (or NO_RECOMMENDATIONS). I can't see this change actually accomplishing
> > anything.
> >
> > Cheers,
> > Paul
> >
>
> Thanks for the quick reply,
> I was using --no-recommends, via the opkg package-manager.
> (rootfs-sandbox).
>
> Regarding the split between RRECOMMENDS and RDEPENDS:
> In my understanding, RRECOMMENDS would be when the functionality is
> optional,
> RDEPENDS when dependency is hard.
Don't forget on RSUGGESTS :)
RDEPENDS - hard dependency
RRECOMMENDS - optional dependency, but good to have in most cases by
default unless it's unavailable (e.g. typical for kernel-modules-*) or
distro/user knows what he is doing and decides to add it in
BAD_RECOMMENDATIONS or removes is on target explicitly
RSUGGESTS - really optional dependency
> To me, this seems like a hard dependency. But a definition between the
> two would be good to have
> for future patches.
>
> Br,
> David
>
>
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2014-02-03 14:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 12:58 [RFC][PATCH] udev: add udev-utils to RDEPENDS David Nyström
2014-02-03 13:03 ` Paul Eggleton
2014-02-03 13:21 ` David Nyström
2014-02-03 14:19 ` Martin Jansa [this message]
2014-02-03 13:43 ` Phil Blundell
2014-02-03 14:01 ` David Nyström
2014-06-03 6:58 ` ChenQi
2014-06-05 23:47 ` Saul Wold
2014-06-06 9:34 ` Koen Kooi
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=20140203141914.GB3698@jama \
--to=martin.jansa@gmail.com \
--cc=david.c.nystrom@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.