From: "Yu, Mingli" <mingli.yu@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/4] groff: add file-homedir-perl to RDEPENDS
Date: Fri, 2 Sep 2016 09:54:05 +0800 [thread overview]
Message-ID: <57C8DBBD.7020701@windriver.com> (raw)
In-Reply-To: <57C00BB4.8050607@windriver.com>
ping
Thanks,
On 2016年08月26日 17:28, Yu, Mingli wrote:
>
>
> On 2016年08月26日 16:55, Burton, Ross wrote:
>>
>> On 26 August 2016 at 03:25, <mingli.yu@windriver.com
>> <mailto: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?
>
> glilypond which is provided by groff transforms sheet music written in
> the lilypond language into the groff language using the .PSPIC request,
> such that groff can transform it into a format that can be displayed
> directly.
>
> 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.
>
> The command glilypond needs File::HomeDir perl module which is provided
> by file-homedir-perl
>
> Thanks,
> Grace
>
>>
>> Ross
next prev parent reply other threads:[~2016-09-02 1:58 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 ` [PATCH 0/4] groff: add file-homedir-perl to RDEPENDS Burton, Ross
2016-08-26 9:28 ` Yu, Mingli
2016-09-02 1:54 ` Yu, Mingli [this message]
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=57C8DBBD.7020701@windriver.com \
--to=mingli.yu@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox