All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Burton, Ross" <ross.burton@intel.com>
To: Mingli Yu <mingli.yu@windriver.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/4] groff: add file-homedir-perl to RDEPENDS
Date: Fri, 26 Aug 2016 09:55:40 +0100	[thread overview]
Message-ID: <CAJTo0Lajz4nb5S5T4rq=F6fmfGvRPEuAyKF=U-OZdWfo+JoOqQ@mail.gmail.com> (raw)
In-Reply-To: <1472178349-32199-1-git-send-email-mingli.yu@windriver.com>

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

On 26 August 2016 at 03:25, <mingli.yu@windriver.com> wrote:

> The series add file-homedir-perl to RDEPENDS for groff as
> glilypond rdepends on File/HomeDir.pm provided by file-homedir-perl
>

Isn't lilypond the music score layout tool?  This seems very specialist.  I
suggest adding the new recipes to meta-perl, and then if someone does want
to use it then the requirements are available.

Unless you're only hitting this because of testing, in which case I'd
suggest skipping this test.

Ross

[-- Attachment #2: Type: text/html, Size: 998 bytes --]

  parent reply	other threads:[~2016-08-26  8:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-26  2:25 [PATCH 0/4] groff: add file-homedir-perl to RDEPENDS mingli.yu
2016-08-26  2:25 ` [PATCH 1/4] " mingli.yu
2016-08-26  2:25 ` [PATCH 2/4] file-homedir-perl: add new recipe mingli.yu
2016-08-26  2:25 ` [PATCH 3/4] file-which-perl: " mingli.yu
2016-08-26  2:25 ` [PATCH 4/4] extutils-makemaker-perl: " mingli.yu
2016-08-26  8:55 ` Burton, Ross [this message]
2016-08-26  9:28   ` [PATCH 0/4] groff: add file-homedir-perl to RDEPENDS Yu, Mingli
2016-09-02  1:54     ` Yu, Mingli
2016-09-02 11:41       ` Richard Purdie
2016-09-05  1:50         ` Yu, Mingli

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='CAJTo0Lajz4nb5S5T4rq=F6fmfGvRPEuAyKF=U-OZdWfo+JoOqQ@mail.gmail.com' \
    --to=ross.burton@intel.com \
    --cc=mingli.yu@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 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.