From: Jose Alarcon <jose.alarcon@ge.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: EXT: Re: [PATCH 2/2] rootfs-postcommands: add test for unsatisfied RRECOMMENDS
Date: Sat, 2 Sep 2017 12:42:57 +0300 [thread overview]
Message-ID: <081604aa-0f5d-e013-672b-c7f93c9dc039@ge.com> (raw)
In-Reply-To: <CAJTo0LZPPuC23W4UnbTYBA8MLZAh1E=8RmU5LeTdVEDpJiQ46Q@mail.gmail.com>
On 02.09.2017 03:22, Burton, Ross wrote:
> On 26 August 2017 at 12:26, Jose Alarcon <jose.alarcon@ge.com
> <mailto:jose.alarcon@ge.com>> wrote:
>
> The do_rootfs log contains a number of unsatisfied package
> recommendations. At the moment those are only visible when
> reviewing the rootfs log.
>
> This patch adds an extra check to surface any unsatisfied
> recommendation as WARNINGS to the build output when
> "debug-tweaks" is enabled.
>
>
> But isn't that the point of recommends?
>
> If the user uses BAD_RECOMMENDATIONS to explicitly stop specific
> recommendations being installed, or the package just isn't available,
> that's fine.
Yes. The purpose of this patch is to surface those unsatisfied
recommends. The user then can decide whether to use BAD_RECOMMENDATIONS,
satisfy the recommend if it is something he needs or just ignore them.
Thanks,
--
Jose
next prev parent reply other threads:[~2017-09-02 9:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-26 11:26 [PATCH 1/2] rootfs-postcommands: remove empty line Jose Alarcon
2017-08-26 11:26 ` [PATCH 2/2] rootfs-postcommands: add test for unsatisfied RRECOMMENDS Jose Alarcon
2017-09-01 6:38 ` Jose Alarcon
2017-09-02 0:22 ` Burton, Ross
2017-09-02 9:42 ` Jose Alarcon [this message]
2017-09-02 11:46 ` Richard Purdie
2017-09-04 5:13 ` EXT: " Jose Alarcon
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=081604aa-0f5d-e013-672b-c7f93c9dc039@ge.com \
--to=jose.alarcon@ge.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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.