From dd9f4c519a4498d0b4a25e2924d2e4926387c2e7 Mon Sep 17 00:00:00 2001
From: Juan RP <xtraeme@gmail.com>
Date: Sat, 16 May 2009 02:14:59 +0200
Subject: [PATCH] Added gdb-6.8 template.

--HG--
extra : convert_revision : a2559f14025f3b38b81511e7283878e6369add81
---
 templates/gdb/template | 41 +++++++++++++++++++++++++++++++++++++++++
 1 file changed, 41 insertions(+)
 create mode 100644 templates/gdb/template

diff --git a/templates/gdb/template b/templates/gdb/template
new file mode 100644
index 0000000000..201846f713
--- /dev/null
+++ b/templates/gdb/template
@@ -0,0 +1,41 @@
+# Template file for 'gdb'
+pkgname=gdb
+version=6.8
+distfiles="http://ftp.gnu.org/gnu/$pkgname/$pkgname-$version.tar.gz"
+build_style=gnu_configure
+configure_args="--disable-werror"
+short_desc="The GNU Debugger"
+maintainer="Juan RP <xtraeme@gmail.com>"
+checksum=a3c5455f30ffb3e6eeafb9e54598b48f9fbf46e3e99f431120360c183ddcc889
+long_desc="
+ The purpose of a debugger such as GDB is to allow you to see what
+ is going on \"inside\" another program while it executes--or what
+ another program was doing at the moment it crashed.
+
+ GDB can do four main kinds of things (plus other things in support
+ of these) to help you catch bugs in the act:
+
+   * Start your program, specifying anything that might affect its
+     behavior.
+
+   * Make your program stop on specified conditions.
+
+   * Examine what has happened, when your program has stopped.
+
+   * Change things in your program, so you can experiment with
+     correcting the effects of one bug and go on to learn about
+     another."
+
+Add_dependency full glibc
+Add_dependency full expat
+Add_dependency build ncurses
+Add_dependency run ncurses-libs
+
+post_install()
+{
+	# resolve conflicts with binutils
+	rm -rf ${DESTDIR}/usr/include ${DESTDIR}/usr/lib
+	for f in bfd configure standards; do
+		rm -f ${DESTDIR}/usr/share/info/${f}.info*
+	done	
+}