Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Peter Tworek <tworaz666@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Paul Menzel <paulepanter@users.sourceforge.net>
Subject: Re: [meta-oe][PATCH] tmux: Add initial recipe for vesion 1.6.
Date: Thu, 02 Feb 2012 20:19:54 +0100	[thread overview]
Message-ID: <4F2AE1DA.2060603@gmail.com> (raw)
In-Reply-To: <1328171236.3941.4.camel@mattotaupa>

On 02/02/2012 09:27 AM, Paul Menzel wrote:
> Dear Peter,
>
>
> thank you for your latest work. It is much appreciated.
You're welcome. Thanks for taking your time to review my patches.
>
> Am Mittwoch, den 01.02.2012, 22:38 +0100 schrieb Peter Tworek:
>
> This is just an optional request from me. I would like to see in the
> commit message what build configuration you used for testing.
No problem. Currently my main target is netbook pro.

>
>> Signed-off-by: Peter Tworek<tworaz666@gmail.com>
>> ---
>>   meta-oe/recipes-extended/tmux/tmux_1.6.bb |   18 ++++++++++++++++++
>>   1 files changed, 18 insertions(+), 0 deletions(-)
>>   create mode 100644 meta-oe/recipes-extended/tmux/tmux_1.6.bb
>>
>> diff --git a/meta-oe/recipes-extended/tmux/tmux_1.6.bb b/meta-oe/recipes-extended/tmux/tmux_1.6.bb
>> new file mode 100644
>> index 0000000..eb6f7df
>> --- /dev/null
>> +++ b/meta-oe/recipes-extended/tmux/tmux_1.6.bb
>> @@ -0,0 +1,18 @@
>> +DESCRIPTION = "Terminal multiplexer"
>> +HOMEPAGE = "http://tmux.sourceforge.net"
>> +SECTION = "console/utils"
>> +
>> +LICENSE = "ISC"
>> +LIC_FILES_CHKSUM = "file://tmux.c;startline=3;endline=17;md5=f36d9c9e6c1c24996a88891fdf783d04"
>> +
>> +DEPENDS = "ncurses libevent"
>> +
>> +SRC_URI = "${SOURCEFORGE_MIRROR}/tmux/${P}.tar.gz"
>> +SRC_URI[md5sum] = "3e37db24aa596bf108a0442a81c845b3"
>> +SRC_URI[sha256sum] = "faee08ba1bd8c22537cd5b7458881d1bdb4985df88ed6bc5967c56881a7efbd6"
>> +
>> +inherit autotools
>> +
>> +do_configure_prepend () {
>> +	sed -i -e 's:-I/usr/local/include::' Makefile.am || bb_fatal "sed failed"
> You can ensure that `sed` is available by depending on `sed-native` I
> think. At least in OE-Classic this was available.
I'll add it in v2. Thanks for pointing that one out.
>
> Additionally it would be great if you could contact upstream and make
> them aware of this problem and maybe even provide a patch. So that in
> the feature no adaptations are needed and other distributions/framework
> can profit too.
Sure, I'll do that. The fix itself is just for QA warning about 
including host headers.

>> +}
>
> Thanks,
>
> Paul
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel



  reply	other threads:[~2012-02-02 19:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01 21:38 [meta-oe][PATCH] tmux: Add initial recipe for vesion 1.6 Peter Tworek
2012-02-02  8:27 ` Paul Menzel
2012-02-02 19:19   ` Peter Tworek [this message]
2012-02-02 19:22 ` [meta-oe][PATCH v2] " Peter Tworek
2012-02-03 17:53   ` Paul Menzel
2012-02-03 23:09     ` Peter Tworek
2012-02-03 23:10 ` [meta-oe][PATCH v3] tmux: Add initial recipe for version 1.6 Peter Tworek
2012-02-04  2:14   ` Khem Raj
2012-02-04  9:55     ` Peter Tworek
2012-02-04 16:41       ` Khem Raj

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=4F2AE1DA.2060603@gmail.com \
    --to=tworaz666@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=paulepanter@users.sourceforge.net \
    /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