void-packages/srcpkgs/gdb/template

45 lines
1.5 KiB
Plaintext
Raw Normal View History

# Template file for 'gdb'
pkgname=gdb
2013-04-27 10:12:03 +02:00
version=7.6
revision=1
build_style=gnu-configure
2012-11-30 05:44:13 +01:00
configure_args="--disable-nls --with-system-readline
--with-system-gdbinit=/etc/gdb/gdbinit"
2013-04-27 10:12:03 +02:00
makedepends="ncurses-devel zlib-devel readline-devel"
short_desc="The GNU Debugger"
maintainer="Juan RP <xtraeme@gmail.com>"
2011-07-30 10:12:00 +02:00
homepage="http://www.gnu.org/software/gdb/"
license="GPL-3"
2012-08-20 11:28:19 +02:00
distfiles="http://ftp.gnu.org/gnu/gdb/gdb-$version.tar.bz2"
2013-04-27 10:12:03 +02:00
checksum=a410e8f35ee70cce83dbbf1da9e2a8373f271ac0e4b71db4336ae293fc7bdf1b
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:
2013-03-13 21:31:55 +01:00
* 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.
2013-03-13 21:31:55 +01:00
* Change things in your program, so you can experiment with correcting the
effects of one bug and go on to learn about another."
2012-01-25 09:15:12 +01:00
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
}
gdb_package() {
conf_files="/etc/gdb/gdbinit"
pycompile_dirs="usr/share/gdb/python/gdb"
pkg_install() {
2013-04-27 10:12:03 +02:00
vmove all
}
}