summarylogtreecommitdiffstats
path: root/digger.ini
diff options
context:
space:
mode:
authorVladimir Panteleev2021-02-26 06:49:02 +0000
committerVladimir Panteleev2021-02-26 06:49:02 +0000
commit827c4c7387fae6faaeb57e8f76094002646101c3 (patch)
tree4f794dbf3fd1570e0b23db505333226fed75e81b /digger.ini
parenta8f77cd122cc211b7cc3b6997aeeb497e898fb78 (diff)
downloadaur-dlang-digger.tar.gz
Remove digger.ini
- Wasn't being installed, anyway - Configures behavior that deviates from upstream - Make consistent with dlang-digger-git
Diffstat (limited to 'digger.ini')
-rw-r--r--digger.ini50
1 files changed, 0 insertions, 50 deletions
diff --git a/digger.ini b/digger.ini
deleted file mode 100644
index 922bad0d4369..000000000000
--- a/digger.ini
+++ /dev/null
@@ -1,50 +0,0 @@
-# Working directory.
-# This directory will contain all of Digger's working files:
-# the D repositories, any build prerequisites obtained
-# automatically, the current build output, and the cache, if
-# enabled.
-# Please specify an absolute path. The default is to use the
-# current directory.
-
-workDir = ~/.cache/digger/
-
-# Build cache.
-# To speed up successive runs, Digger can save the results of
-# each commit's build. The downside is that this uses up disk
-# space. The following cache engines are available:
-# - none No persistent cache.
-# - directory Store built files in a directory tree.
-# Saves some disk space by hard-linking identical
-# files.
-# - git Use a git repository (and git's deduplication /
-# compression mechanisms). Uses much less disk
-# space than "directory", but is a little slower.
-# You can periodically run "digger compact" to optimize disk
-# space used by the cache.
-
-cache = git
-
-# Build/test environment.
-# By default, Digger completely clears the environment and
-# builds a new one from scratch, to avoid potential sources
-# of contamination that can affect the D builds or test results.
-# The environment is calculated in this order:
-# 1. Clear entirely
-# 2. Build minimal environment
-# 3. Apply digger.ini settings
-# 4. Apply bisect.ini settings, if we are bisecting
-# Step 4 is only applied during the execution of the test command.
-
-[environment]
-
-# You can use %VAR% syntax to refer to the previous value of a
-# variable, or if there wasn't one, to the value from the
-# original environment (before it was cleared and rebuilt).
-
-# Examples:
-
-# Add something to PATH
-#PATH=%PATH%;C:\Tools
-
-# Import PATHEXT from the original environment
-#PATHEXT=%PATHEXT%