           SPELL=openslp
if [ "$GETDEVEL" == "y" ]; then
         VERSION=1.3.0
     SOURCE_HASH=sha512:17ec053464d7636e7cce424094ceb4ea8caa038267b1c15bbd1e7cae1e3e8a1388e2bf72936a97688f6866cee93d14c21eae897ec2a511f49aebdbb5fd2ab5c4
else
         VERSION=1.2.1
     SOURCE_HASH=sha512:34742d88e772d7dba5c6fab1ccb7bf27d6174c5ca429aec406472994bcd806bfaf16dd86fce2ae4c51659587e99cced2436cf36772f6e086f7b87275fb1b19b6
fi
          SOURCE=${SPELL}-${VERSION}.tar.gz
SOURCE_DIRECTORY=${BUILD_DIRECTORY}/${SPELL}-${VERSION}
   SOURCE_URL[0]=http://downloads.sourceforge.net/sourceforge/${SPELL}/${SOURCE}
      LICENSE[0]=BSD
        WEB_SITE=http://www.openslp.org
         ENTERED=20041002
        KEYWORDS="net"
           SHORT="A IETF Service Location Protocol library"
cat << EOF
Service Location Protocol is an IETF standards track protocol 
that provides a framework to allow networking applications to 
discover the existence, location, and configuration of networked 
services in enterprise networks.  Traditionally, in order to 
locate services on the network, users of network applications 
have been required to supply the host name or network address of 
the machine that provides a desired service.  Ensuring that 
users and applications are supplied with the correct information 
has, in many cases, become an administrative nightmare.

Protocols that support service location are often taken for granted, 
mostly because they are already included (without fanfare) in many 
network operating systems. For example, without Microsoft's SMB 
service location facilities, "Network Neighborhood" could not 
discover services available for use on the network and Novell NetWare 
would be unable to locate NDS trees.  Nevertheless, an IETF service 
location protocol was not standardized until the advent of SLP.  
Because it is not tied to a proprietary technology, SLP provides a 
service location solution that could become extremely important 
(especially on Unix) platforms. 
EOF
