3fa6be1fef
Like with the network-uri split, cabal will automatically turn off the flag when building with an old network. I have not tested building with the new network-3.0.0.0 yet; several other dependencies including aws are still pinned on network-2.*
29 lines
509 B
YAML
29 lines
509 B
YAML
flags:
|
|
git-annex:
|
|
production: true
|
|
assistant: true
|
|
pairing: true
|
|
s3: true
|
|
webdav: true
|
|
torrentparser: true
|
|
webapp: true
|
|
magicmime: false
|
|
dbus: false
|
|
debuglocks: false
|
|
benchmark: false
|
|
networkbsd: false
|
|
packages:
|
|
- '.'
|
|
extra-deps:
|
|
- aws-0.17.1
|
|
- bloomfilter-2.0.1.0
|
|
- torrent-10000.1.1
|
|
- Win32-2.6.1.0
|
|
- directory-1.3.1.5
|
|
- process-1.6.2.0
|
|
- http-client-0.5.7.1
|
|
- unix-compat-0.5.0.1
|
|
allow-newer: true
|
|
explicit-setup-deps:
|
|
git-annex: true
|
|
resolver: lts-9.10
|