LBRYCommunity/lbcd
1
0
Fork 0
Code Issues 17 Pull requests 4 Projects Releases 28 Packages Wiki Activity
lbcd/glide.yaml

36 lines
824 B
YAML
Raw Normal View History

build: Convert project to use glide. (#689) This converts the project to allow btcd to be used with the glide package manager in order to provide stable and reproducible builds without the user having to jump through all of the hoops as they do today. It consists of adding a glide.yaml file which identifies the project dependencies and locations along with a glide.lock file which contains the complete dependency tree pinned to specific versions. Glide uses these files to download the packages (or updates) to a local vendor directory and checkout the correct pinned versions. The go tool, in turn, is used to build/install btcd and will use the pinned versions in the vendor directory. This also updates TravisCI to build using glide, removes some of the exceptions in the lint checks which are no longer required, and updates the README.md with the new instructions needed to build the project with glide.
2016-05-06 17:47:53 +02:00
package: github.com/btcsuite/btcd
import:
- package: github.com/btcsuite/btclog
travis: test against latest patch release.
2017-01-11 21:54:27 +01:00
- package: github.com/btcsuite/btcrpcclient
build: Convert project to use glide. (#689) This converts the project to allow btcd to be used with the glide package manager in order to provide stable and reproducible builds without the user having to jump through all of the hoops as they do today. It consists of adding a glide.yaml file which identifies the project dependencies and locations along with a glide.lock file which contains the complete dependency tree pinned to specific versions. Glide uses these files to download the packages (or updates) to a local vendor directory and checkout the correct pinned versions. The go tool, in turn, is used to build/install btcd and will use the pinned versions in the vendor directory. This also updates TravisCI to build using glide, removes some of the exceptions in the lint checks which are no longer required, and updates the README.md with the new instructions needed to build the project with glide.
2016-05-06 17:47:53 +02:00
- package: github.com/btcsuite/btcutil
subpackages:
- bloom
build: update dependancies required by rpctest
2016-08-20 00:42:07 +02:00
- hdkeychain
build: Convert project to use glide. (#689) This converts the project to allow btcd to be used with the glide package manager in order to provide stable and reproducible builds without the user having to jump through all of the hoops as they do today. It consists of adding a glide.yaml file which identifies the project dependencies and locations along with a glide.lock file which contains the complete dependency tree pinned to specific versions. Glide uses these files to download the packages (or updates) to a local vendor directory and checkout the correct pinned versions. The go tool, in turn, is used to build/install btcd and will use the pinned versions in the vendor directory. This also updates TravisCI to build using glide, removes some of the exceptions in the lint checks which are no longer required, and updates the README.md with the new instructions needed to build the project with glide.
2016-05-06 17:47:53 +02:00
- package: github.com/btcsuite/go-socks
subpackages:
- socks
multi: Switch to upstream golang.org/x/crypto. Now that glide is used for version management and a specific commit of the upstream repository can be locked it is no longer necessary to maintain a fork of the package specifically to keep a stable dependency. While here, update the glide dependency for btcutil as well since it was switched to use the upstream path as well.
2017-05-09 05:58:32 +02:00
- package: golang.org/x/crypto
build: Convert project to use glide. (#689) This converts the project to allow btcd to be used with the glide package manager in order to provide stable and reproducible builds without the user having to jump through all of the hoops as they do today. It consists of adding a glide.yaml file which identifies the project dependencies and locations along with a glide.lock file which contains the complete dependency tree pinned to specific versions. Glide uses these files to download the packages (or updates) to a local vendor directory and checkout the correct pinned versions. The go tool, in turn, is used to build/install btcd and will use the pinned versions in the vendor directory. This also updates TravisCI to build using glide, removes some of the exceptions in the lint checks which are no longer required, and updates the README.md with the new instructions needed to build the project with glide.
2016-05-06 17:47:53 +02:00
subpackages:
- ripemd160
- package: github.com/btcsuite/goleveldb
subpackages:
- leveldb
- leveldb/comparer
- leveldb/errors
- leveldb/filter
- leveldb/iterator
- leveldb/opt
- leveldb/util
- package: github.com/btcsuite/websocket
- package: github.com/btcsuite/winsvc
subpackages:
- eventlog
- mgr
- svc
- package: github.com/davecgh/go-spew
subpackages:
- spew
Drop btcsuite/go-flags in favor of upstream
2016-12-09 18:54:33 +01:00
- package: github.com/jessevdk/go-flags
version: 1679536dcc895411a9f5848d9a0250be7856448c
all: Remove seelog logger. The btclog package has been changed to defining its own logging interface (rather than seelog's) and provides a default implementation for callers to use. There are two primary advantages to the new logger implementation. First, all log messages are created before the call returns. Compared to seelog, this prevents data races when mutable variables are logged. Second, the new logger does not implement any kind of artifical rate limiting (what seelog refers to as "adaptive logging"). Log messages are outputted as soon as possible and the application will appear to perform much better when watching standard output. Because log rotation is not a feature of the btclog logging implementation, it is handled by the main package by importing a file rotation package that provides an io.Reader interface for creating output to a rotating file output. The rotator has been configured with the same defaults that btcd previously used in the seelog config (10MB file limits with maximum of 3 rolls) but now compresses newly created roll files. Due to the high compressibility of log text, the compressed files typically reduce to around 15-30% of the original 10MB file.
2017-05-24 23:24:06 +02:00
- package: github.com/jrick/logrotate
Reference in a new issue Copy permalink