split config into separate conf file

1 files changed, 81 insertions, 0 deletions

diff --git a/sbosrcarch.conf b/sbosrcarch.conf
new file mode 100644
index 0000000..298011c
--- /dev/null
+++ b/sbosrcarch.conf
@@ -0,0 +1,81 @@
+#!/usr/bin/perl
+
+## Config file for sbosrcarch. The #! line above is just for syntax
+# highlighting while editing this file, it's not a standalone perl
+# script.
+
+# This file must be called either sbosrcarch.conf or .sbosrcarch.conf,
+# and located in current directory, $HOME, /etc/sbosrcarch, or /etc.
+# It's parsed by perl, so it needs to be valid perl code. If in doubt,
+# try 'perl -c sbosrcarch.conf' to check the syntax.
+
+# Rest of file is config values and (hopefully) explanatory comments.
+
+## $sbogiturl (string)
+# slackbuilds.org's master git URL (used with 'git clone').
+# Unlikely that this will ever need to be changed.
+$sbogiturl = "git://slackbuilds.org/slackbuilds.git";
+
+## $sbogitdir (string, filesystem path)
+# Location of local copy of SBo git clone. 'sbosrcarch create' will create
+# this via 'git clone' if it doesn't already exist. Should stay on master
+# branch. This script will take care of pulling from SBo git, so this
+# dir shouldn't be your working repo that you use for any other purpose.
+# This must be located on the same filesystem as $archivedir!
+$sbogitdir = "/home/urchlay/sbo-master/";
+
+# Branch to use, normally master (only change for testing purposes).
+#$sbogitbranch = "master"; $ TODO: implement
+
+## $archivedir (string, filesystem path)
+# Location of archive (which you will serve by e.g. apache).
+# This must be located on the same filesystem as $sbogitdir!
+$archivedir = "/home/urchlay/sboarchive";
+
+## $maxfilemegs (positive real number)
+# Max file size, in megabytes (real ones, 2**10). Doesn't have to be an
+# integer. Set to 0 for "no limit". Files larger than this (according to
+# HTTP HEAD or FTP SIZE) won't be downloaded. If you increase this, re-run
+# 'sbosrcarch create' after editing this config. If you decrease it,
+# run 'sbosrcarch trim' to get rid of files that are now over the limit.
+$maxfilemegs = 0.1;
+
+## $symlinks (boolean)
+# 0 = use hard links for by-md5 tree, 1 = symlinks.
+# Which should you use? Well, if other people are going to rsync your
+# repo, hardlinks are more expensive (see the -a and -H options
+# in the rsync man page). If disk space is at a premium, symlinks
+# eat a tiny bit more space (but I mean *tiny*)... and you'll have to
+# make sure your web server follows symlinks if you use them.
+# TODO: implement this! For now, only hard links are supported.
+$symlinks = 0;
+
+## $wgetargs (string)
+# Extra arguments to pass to wget. We're already creating a config file
+# and using it in place of .wgetrc and /etc/wgetrc, you don't need to
+# list --config here.
+$wgetargs = "";
+
+## $wgetrc_contents (string, see "man wget" for more information)
+# We don't trust the system-wide or user wgetrc, so we provide our own.
+# The check_certificate = off might be controversial. My take on it is
+# that it's better to download the file even if the server has a crappy
+# self-signed certificate.
+# Might want to add this here:
+#timeout = 30
+$wgetrc_contents = <<EOF;
+robots = off
+user_agent = Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
+check_certificate = off
+content_disposition = off
+EOF
+
+## %user_agent_overrides (hash, keys = regexes, values = strings)
+# Most download sites work better if the HTTP user agent header is
+# set to a normal browser (see $wgetrc_contents above). But some sites
+# "helpfully" redirect to an HTML page if using a browser, so list them
+# here.
+%user_agent_overrides = (
+		qr/(?:sourceforge|sf)\.net/ => 'wget',
+);
+