From: Saul Wold <sgw@linux.intel.com>
To: Chris Larson <kergoth@gmail.com>
Cc: Christopher Larson <chris_larson@mentor.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] lzop-1.03: add recipe
Date: Thu, 08 Dec 2011 09:21:21 -0800 [thread overview]
Message-ID: <4EE0F211.7000402@linux.intel.com> (raw)
In-Reply-To: <CABcZANnO4_t7HxV5BuTNSjjaK=QOGCh2iKxYSkES33Qw7-eHzA@mail.gmail.com>
On 12/08/2011 08:55 AM, Chris Larson wrote:
> On Thu, Dec 8, 2011 at 9:49 AM, Saul Wold<sgw@linux.intel.com> wrote:
>> On 12/05/2011 02:13 PM, Christopher Larson wrote:
>>>
>>> From: Christopher Larson<chris_larson@mentor.com>
>>>
>>> This is needed by some kernels when CONFIG_KERNEL_LZO=y (specifically,
>>> given
>>> the current defconfig, this affects linux-omap4 2.6 in the meta-ti layer).
>>>
>>> Signed-off-by: Christopher Larson<chris_larson@mentor.com>
>>> ---
>>> meta/recipes-support/lzop/lzop/acinclude.m4 | 390
>>> +++++++++++++++++++++++++++
>>> meta/recipes-support/lzop/lzop_1.03.bb | 25 ++
>>> 2 files changed, 415 insertions(+), 0 deletions(-)
>>> create mode 100644 meta/recipes-support/lzop/lzop/acinclude.m4
>>> create mode 100644 meta/recipes-support/lzop/lzop_1.03.bb
>>>
>>
>> <SNIP>
>>
>>
>>> diff --git a/meta/recipes-support/lzop/lzop_1.03.bb
>>> b/meta/recipes-support/lzop/lzop_1.03.bb
>>> new file mode 100644
>>> index 0000000..d0cb842
>>> --- /dev/null
>>> +++ b/meta/recipes-support/lzop/lzop_1.03.bb
>>> @@ -0,0 +1,25 @@
>>> +SUMMARY = "Real-time file compressor"
>>> +DESCRIPTION = "lzop is a compression utility which is designed to be a
>>> companion to gzip. \n\
>>> +It is based on the LZO data compression library and its main advantages
>>> over \n\
>>> +gzip are much higher compression and decompression speed at the cost of
>>> some \n\
>>> +compression ratio. The lzop compression utility was designed with the
>>> goals \n\
>>> +of reliability, speed, portability and with reasonable drop-in
>>> compatibility \n\
>>> +to gzip."
>>> +DEPENDS += "lzo"
>>> +PR = "r0"
>>> +
>>> +LICENSE = "GPLv2+"
>>> +LIC_FILES_CHKSUM = "file://COPYING;md5=dfeaf3dc4beef4f5a7bdbc35b197f39e \
>>> +
>>> file://src/lzop.c;beginline=5;endline=21;md5=6797bd3ed0a1a49327b7ebf9366ebd86"
>>> +
>>> +SRC_URI = "http://www.lzop.org/download/${BP}.tar.gz \
>>
>> I think this ------------------------------- ^^
>> should really be ${BPN}-${PV} which make is much easier to do updates with
>> by just changing the file name.
>
> I think you're confused. BP *is* ${BPN}-${PV}. What exactly is the
> problem with using it?
>
My bad, I thought it was something else, thanks for continuing my training!
Sau!
>
>>> + file://acinclude.m4"
>>> +
>>
>> NO SRC_URI Checksums!
>
> Gah, damnit.
prev parent reply other threads:[~2011-12-08 17:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 22:13 [PATCH v2] lzop-1.03: add recipe Christopher Larson
2011-12-08 16:49 ` Saul Wold
2011-12-08 16:55 ` Chris Larson
2011-12-08 17:21 ` Saul Wold [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=4EE0F211.7000402@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=chris_larson@mentor.com \
--cc=kergoth@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox