Ready SlackBuild

Ready SlackBuild allows you to download the source package and otherwise prepare to run a Slackbuild script that conforms to standards set by the maintainers of SlackBuilds.org. In particular, Ready SlackBuild reads the info file to find the download location, check the md5sum and therefore the info file must exist.

An info file usually looks like this:

		PRGNAM="R"
		VERSION="2.9.0"
		HOMEPAGE="http://www.r-project.org"
		DOWNLOAD="http://mirrors.ibiblio.org/pub/mirrors/CRAN/src/base/R-2/R-2.9.0.tar.gz"
		MD5SUM="a5b79a2bc1372136cda4674b5f46d146"
		MAINTAINER="Joel J. Adamson"
		EMAIL="adamsonj@email.unc.edu"
	      

Ready SlackBuild is self-hosting: download this file and untar it, then just enter

		#> ./rsb.sh
	      

at the prompt and it will download the necessary tarball and check the md5sum. You can then run the SlackBuild to build the package.

Ready SlackBuild allows me to enter a SlackBuild application directory and enter

		#> rsb
	      

to download the source package, check the md5sum, and make the SlackBuild itself executable. After rsb runs without errors, I can simply run the SlackBuild to build the package.

		  #! /bin/sh
		  # put this in ~/.cron.daily
		  #
		  # It will mirror Slackbuilds.org, so that you can just go to a
		  # directory in the tree and build the slackbuild, without having to
		  # download it.
		  DEST=$HOME/SlackBuilds/12.2

		  # update the collection
		  rsync --update --delete -av \
		  rsync://rsync.slackbuilds.org/slackbuilds/12.2/ \
		  $DEST

		  ########################################################################
		

If you encounter problems in running rsb that do not appear to be your own errors, please contact me at <adamsonj@email.unc.edu>. I also welcome suggestions, but features will be implemented in accordance with the priority that they have to my own usage (in other words, if you have a better idea about how to do this, please convince me to do it differently).