#!/bin/sh ############################# ## Build script for: ngrep ## Creator: kaneda@bohater.net ## Date: 12 Dec 04 ## Builds package: Yes ## Source location: http://ngrep.sourceforge.net/ ## Downloads Source: Yes ## Build script version: 1.0 ## Requirements: None ## ## Notes: Any special notes the person may need to edit this file. ## ## Include the slackware-pkg conf file if [ -a /etc/slack-package.conf ]; then . /etc/slack-package.conf else echo "Sorry you need to have the slack-package.conf file to run these" echo "please install the slackbuilds package from LinuxPackages.net" exit fi ## Lets set the name of the program here so we can use it later. NAME=ngrep ## Set the versions for packages here, these must match the source file version. PROGRAM_VER=1.44 ## Set the BUILD the $MYIN comes from the global config file in /etc BUILD=1$MYIN ## Location to download the source SRC_LOC="http://switch.dl.sourceforge.net/sourceforge/ngrep/$NAME-$PROGRAM_VER.tar.bz2" ## Set initial variables these should be standard in most packages: PKG=$TMP/package-$NAME ## Now we go grab the source for the user. Again global config has the wget line ## We will check if it is here and if not then download if [ -a $CWD/$NAME-$PROGRAM_VER.tar.bz2 ]; then echo "Source present not downloading" else $WGET $SRC_LOC || true fi ## Ok time to make sure the area is clean and unarchive the file rm -rf $PKG mkdir -p $PKG cd $TMP rm -rf $NAME-$PROGRAM_VER tar jxvf $CWD/$NAME-$PROGRAM_VER.tar.bz2 ## Now from this point on we do all the package prep and building. I like to organize them in sections ## like compile, prepare, description, build like below as an example compile() { cd $TMP/$NAME-$PROGRAM_VER chown -R root.root . if [ ! -f /usr/lib/gcc-lib/i486-slackware-linux/3.2.3/include/net/bpf.h ] && \ [ ! -f /usr/include/net/bpf.h ] ; then ln -s /usr/include/pcap-bpf.h /usr/include/net/bpf.h fi export CFLAGS=$SLKCFLAGS ./configure --prefix=/usr --mandir=/man make make install DESTDIR=$PKG } ## The next area I use for getting the documents set and maybe config files. prepare() { mkdir -p $PKG/usr/doc/$NAME-$PROGRAM_VER cp -fr $TMP/$NAME-$PROGRAM_VER/doc/* $PKG/usr/doc/$NAME-$PROGRAM_VER/ cp -fr $TMP/$NAME-$PROGRAM_VER/scripts/ $PKG/usr/doc/$NAME-$PROGRAM_VER/ mv -f $PKG/usr/share/man $PKG/usr/man rm -rf $PKG/usr/share/ ##Some functions from the global config to help with the cleanup ( cd $PKG strip_bin # Strips the libs files reduces the size and removes unneeded cruft strip_lib ) # Every good package should gzip those man pages gzip_man $PKG # Set group ownership for the bin directory bin_perms $PKG # Set group ownership for the sbin directory #sbin_perms $PKG } ## The next area is for the description. You can use this method or just cat a slack-desc file into ## the install area. I will use apache here as a sample description() { mkdir -p $PKG/install cat > $PKG/install/slack-desc << END |-----handy-ruler------------------------------------------------------| ngrep: $NAME $PROGRAM_VER (network grep) ngrep: ngrep: ngrep strives to provide most of GNU grep's common features, applying ngrep: them to the network layer. ngrep is a pcap-aware tool that will allow ngrep: you to specify extended regular or hexadecimal expressions to match ngrep: against data payloads of packets. It currently recognizes IPv4/6, TCP, ngrep: UDP and ICMPv4/6, IGMP and Raw across Ethernet, PPP, SLIP, FDDI, Token ngrep: Ring and null interfaces, and understands bpf filter logic in the same ngrep: fashion as more common packet sniffing tools, such as tcpdump and ngrep: snoop. ngrep: My other Slack packages: http://kaneda.bohater.net/slackware END } ## The last part is the build build() { # Build the package: cd $PKG makepkg -l y -c n $TMP/$NAME-$PROGRAM_VER-$ARCH-$BUILD.tgz mv $TMP/$NAME-$PROGRAM_VER-$ARCH-$BUILD.tgz $PKG_DIR/ echo "Your $NAME package is complete, make sure you open it up before installing it." echo "It is located in $PKG_DIR thanks for your support The Linuxpackages.net Folks" } ### Now we call all those functions in order compile prepare description build