All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCHv4 2/3] liblockdev: new recipe, new version of libcec requires it
Date: Wed, 05 Sep 2012 16:49:13 +0100	[thread overview]
Message-ID: <50477479.70400@communistcode.co.uk> (raw)
In-Reply-To: <CAK18fxG8PpuVYW0UXZwRKghn1duy2FwhL2RWt_cP82XX33srcA@mail.gmail.com>

On 05/09/12 16:41, Andrei Gherzan wrote:
> On Wed, Sep 5, 2012 at 6:21 PM, <ml@communistcode.co.uk> wrote:
>
>> From: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk>
>>
>> V4
>>
>> - Remove debian packaging patch, it is not needed
>>
>>
> What means it is not needed anymore? Included in upstream? Fixed in yocto?
>
>
>> Signed-off-by: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk>
>> ---
>>   .../liblockdev/liblockdev_1.0.3.bb                 | 26
>> ++++++++++++++++++++++
>>   1 file changed, 26 insertions(+)
>>   create mode 100644 meta-oe/recipes-extended/liblockdev/
>> liblockdev_1.0.3.bb
>>
>>
> Where is the removed patch?
>
>
>> diff --git a/meta-oe/recipes-extended/liblockdev/liblockdev_1.0.3.bbb/meta-oe/recipes-extended/liblockdev/
>> liblockdev_1.0.3.bb
>> new file mode 100644
>> index 0000000..be5ce44
>> --- /dev/null
>> +++ b/meta-oe/recipes-extended/liblockdev/liblockdev_1.0.3.bb
>> @@ -0,0 +1,26 @@
>> +DESCRIPTION = "Manage character and block device lockfiles."
>> +HOMEPAGE = "
>> http://anonscm.debian.org/gitweb/?p=lockdev/lockdev.git;a=summary"
>> +
>> +LICENSE = "LGPLv2.1"
>> +LIC_FILES_CHKSUM = "file://LICENSE;md5=d8045f3b8f929c1cb29a1e3fd737b499"
>> +
>> +PV = "1.0.3"
>> +
>> +SRC_URI = "
>> http://ftp.de.debian.org/debian/pool/main/l/lockdev/lockdev_${PV}.orig.tar.gz
>> "
>> +
>> +SRC_URI[md5sum] = "64b9c1b87b125fc348e892e24625524a"
>> +SRC_URI[sha256sum] =
>> "ccae635d7ac3fdd50897eceb250872b3d9a191d298f213e7f0c836910d869f82"
>> +
>> +S = "${WORKDIR}/lockdev-${PV}"
>> +
>> +do_compile() {
>> +  oe_runmake CC="${CC}" LD="${LD}" shared
>> +}
>> +
>> +do_install() {
>> +  oe_runmake basedir="${D}" incdir="${D}${includedir}"
>> libdir="${D}${libdir}" install_dev
>> +}
>> +
>> +FILES_{PN} = "${includedir}/* \
>> +              ${libdir}/* \
>> +"
>> --
>> 1.7.12
>>
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Sorry, this has been confusing!

I had erroneously added a patch in my V1 git send-patch for building 
liblockdev which wasn't required so I removed it and rebased my patches 
without it.

-- 

   Jack Mitchell (jack@embed.me.uk)
   Embedded Systems Engineer
   http://www.embed.me.uk

--




  reply	other threads:[~2012-09-05 16:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-05 15:21 [PATCHv4 1/3] libplist: add upstream patch to fix parallel make issue ml
2012-09-05 15:21 ` [PATCHv4 2/3] liblockdev: new recipe, new version of libcec requires it ml
2012-09-05 15:41   ` Andrei Gherzan
2012-09-05 15:49     ` Jack Mitchell [this message]
2012-09-05 15:50       ` Andrei Gherzan
2012-09-06 11:16   ` Koen Kooi
2012-09-06 11:22     ` Jack Mitchell
2012-09-05 15:21 ` [PATCHv4 3/3] libcec: update libcec to latest version (1.8.1) as to include RasPi support ml
2012-09-06  8:52 ` [PATCHv4 1/3] libplist: add upstream patch to fix parallel make issue Jack Mitchell
2012-09-06 10:54   ` Koen Kooi
2012-09-06 11:17 ` Koen Kooi

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=50477479.70400@communistcode.co.uk \
    --to=ml@communistcode.co.uk \
    --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.