From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] p4: remove broken and 4 years old recipes.
Date: Wed, 15 Sep 2010 14:20:43 -0400 [thread overview]
Message-ID: <4C910E7B.8030601@balister.org> (raw)
In-Reply-To: <AANLkTim9Tt1rqMPkz2YFYEr296_XNwT7GMfBCBLCmV5f@mail.gmail.com>
On 09/15/2010 02:08 PM, Khem Raj wrote:
> On Wed, Sep 15, 2010 at 5:02 AM, Philip Balister<philip@balister.org> wrote:
>> On 09/15/2010 02:32 AM, Frans Meulenbroeks wrote:
>>>
>>> 2010/9/15 Graham Gower<graham.gower@gmail.com>:
>>>>
>>>> Recipes are broken for all architectures except one (probably arm)
>>>> because the files in the SRC_URI depend on TARGET_ARCH and the md5/sha256
>>>> are presumably valid only for one of these.
>>>>
>>>> Anyone wanting perforce should submit new recipes for new perforce
>>>> versions.
>>>>
>>>> Signed-off-by: Graham Gower<graham.gower@gmail.com>
>>>
>>> Agree with the reasoning of Graham, so:
>>>
>>> Acked-by: Frans Meulenbroeks<fransmeulenbroeks@gmail.com>
>>>
>>> Actually I am not too keen on having recipes that just "install" an
>>> externally downloaded binary blob
>>> (and functionally speaking this does not seem to be something for an
>>> embedded system either)
>>
>> I will have a need for a recipe to install binary blobs (fpga bin files)
>> into a file system at some point. So this class recipes are needed.
>>
>
> do you need these m4 recipes ?
My comments where of a general nature, not about the specific case.
Philip
>
>> Philip
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
>
>
>
prev parent reply other threads:[~2010-09-15 18:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 0:27 [PATCH] p4: remove broken and 4 years old recipes Graham Gower
2010-09-15 6:32 ` Frans Meulenbroeks
2010-09-15 12:02 ` Philip Balister
2010-09-15 12:23 ` Frans Meulenbroeks
2010-09-15 18:08 ` Khem Raj
2010-09-15 18:20 ` Philip Balister [this message]
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=4C910E7B.8030601@balister.org \
--to=philip@balister.org \
--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 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.