# Template file for 'gdb' pkgname=gdb version=7.4.1 distfiles="http://ftp.gnu.org/gnu/gdb/gdb-$version.tar.bz2" build_style=gnu-configure configure_args="--disable-nls --with-system-readline --with-system-gdbinit=/etc/gdb/gdbinit" makedepends="ncurses-devel zlib-devel readline-devel python-devel" revision=1 short_desc="The GNU Debugger" maintainer="Juan RP " homepage="http://www.gnu.org/software/gdb/" license="GPL-3" checksum=a081343c017732ab4dd30a4730da83667aa01b0b37d1ad3700c3f05a5da0f9f6 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." pycompile_dirs="usr/share/gdb/python/gdb" conf_files="/etc/gdb/gdbinit" post_install() { # resolve conflicts with binutils rm -rf ${DESTDIR}/usr/include ${DESTDIR}/usr/lib [ -d ${DESTDIR}/usr/lib64 ] && rm -rf ${DESTDIR}/usr/lib64 for f in bfd configure standards; do rm -f ${DESTDIR}/usr/share/info/${f}.info* done }