All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Benard <eric@eukrea.com>
To: openembedded-devel@lists.openembedded.org
Subject: [PATCH] nano: Add version 2.2.4.
Date: Thu, 29 Apr 2010 16:01:34 +0200	[thread overview]
Message-ID: <1272549694-23764-1-git-send-email-eric@eukrea.com> (raw)

* give access to the latest stable release available
* Tested on x86

Signed-off-by: Eric Benard <eric@eukrea.com>
---
 recipes/nano/nano_2.2.4.bb |   22 ++++++++++++++++++++++
 1 files changed, 22 insertions(+), 0 deletions(-)
 create mode 100644 recipes/nano/nano_2.2.4.bb

diff --git a/recipes/nano/nano_2.2.4.bb b/recipes/nano/nano_2.2.4.bb
new file mode 100644
index 0000000..561b64e
--- /dev/null
+++ b/recipes/nano/nano_2.2.4.bb
@@ -0,0 +1,22 @@
+DESCRIPTION = "GNU nano (Nano's ANOther editor, or \
+Not ANOther editor) is an enhanced clone of the \
+Pico text editor."
+HOMEPAGE = "http://www.nano-editor.org/"
+LICENSE = "GPLv2"
+SECTION = "console/utils"
+DEPENDS = "ncurses"
+
+SRC_URI = "http://www.nano-editor.org/dist/v2.2/nano-${PV}.tar.gz \
+           file://glib.m4"
+
+inherit autotools
+
+# only 16K more to get everything but the kitchen sink
+EXTRA_OECONF = "--enable-all"
+
+do_configure_prepend () {
+	install -m 0644 ${WORKDIR}/glib.m4 m4/
+}
+
+SRC_URI[md5sum] = "6304308afb1f7ef4a5e93eb99206632a"
+SRC_URI[sha256sum] = "971b8547be157de5a814cb26c804dc2515b686d7188f4dc016269312965d4da5"
-- 
1.6.3.3




             reply	other threads:[~2010-04-29 14:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-29 14:01 Eric Benard [this message]
2010-05-02 12:25 ` [PATCH] nano: Add version 2.2.4 Roman I Khimov
  -- strict thread matches above, loose matches on Subject: below --
2010-04-17  5:17 Scott Garman
2010-04-18 10:04 ` Paul Menzel
2010-05-02 12:22 ` Roman I Khimov
2010-05-02 21:24   ` Scott Garman

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=1272549694-23764-1-git-send-email-eric@eukrea.com \
    --to=eric@eukrea.com \
    --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.