mirrors/lnd
1
0
Fork 0
mirror of https://github.com/lightningnetwork/lnd.git synced 2024-11-20 10:39:01 +01:00
Code Issues Projects Releases Wiki Activity
1dfda91415
lnd/glide.yaml

65 lines
1.5 KiB
YAML
Raw Normal View History

add glide dependency management for fully reproducible builds This commit adds glide integration in order to make lnd builds fully reproducible. Rather than using “go get” users should now manually pull down the repo, use glide to fetch+install the dependancies, then manually install all related binaries. With this change we no longer have to chase dependancies making breaking API changes under us. We can manually update the managed dependancies once a new stable release of a defendant package is released. Additionally, reproducible builds are a strong requirement in order to securely distribute future major releases of lnd.
2016-07-23 03:52:36 +02:00
package: github.com/lightningnetwork/lnd
import:
- package: github.com/boltdb/bolt
version: ^1.2.1
- package: github.com/btcsuite/btclog
- package: github.com/btcsuite/fastsha256
- package: github.com/btcsuite/go-flags
- package: github.com/btcsuite/seelog
version: ^2.1.0
- package: github.com/davecgh/go-spew
subpackages:
- spew
- package: github.com/golang/protobuf
subpackages:
- proto
- package: github.com/howeyc/gopass
- package: github.com/roasbeef/btcd
build: update glide dependancies since roasbeef/btcsuite upstream merge
2017-01-05 23:08:22 +01:00
version: master
add glide dependency management for fully reproducible builds This commit adds glide integration in order to make lnd builds fully reproducible. Rather than using “go get” users should now manually pull down the repo, use glide to fetch+install the dependancies, then manually install all related binaries. With this change we no longer have to chase dependancies making breaking API changes under us. We can manually update the managed dependancies once a new stable release of a defendant package is released. Additionally, reproducible builds are a strong requirement in order to securely distribute future major releases of lnd.
2016-07-23 03:52:36 +02:00
subpackages:
- blockchain
- btcec
- btcjson
- chaincfg
- txscript
- wire
build: update glide dependancies since roasbeef/btcsuite upstream merge
2017-01-05 23:08:22 +01:00
- connmgr
add glide dependency management for fully reproducible builds This commit adds glide integration in order to make lnd builds fully reproducible. Rather than using “go get” users should now manually pull down the repo, use glide to fetch+install the dependancies, then manually install all related binaries. With this change we no longer have to chase dependancies making breaking API changes under us. We can manually update the managed dependancies once a new stable release of a defendant package is released. Additionally, reproducible builds are a strong requirement in order to securely distribute future major releases of lnd.
2016-07-23 03:52:36 +02:00
- package: github.com/roasbeef/btcrpcclient
build: update glide to ensure the package hash verifies properly
2016-12-13 00:55:15 +01:00
version: master
add glide dependency management for fully reproducible builds This commit adds glide integration in order to make lnd builds fully reproducible. Rather than using “go get” users should now manually pull down the repo, use glide to fetch+install the dependancies, then manually install all related binaries. With this change we no longer have to chase dependancies making breaking API changes under us. We can manually update the managed dependancies once a new stable release of a defendant package is released. Additionally, reproducible builds are a strong requirement in order to securely distribute future major releases of lnd.
2016-07-23 03:52:36 +02:00
- package: github.com/roasbeef/btcutil
build: update glide dependancies since roasbeef/btcsuite upstream merge
2017-01-05 23:08:22 +01:00
version: master
add glide dependency management for fully reproducible builds This commit adds glide integration in order to make lnd builds fully reproducible. Rather than using “go get” users should now manually pull down the repo, use glide to fetch+install the dependancies, then manually install all related binaries. With this change we no longer have to chase dependancies making breaking API changes under us. We can manually update the managed dependancies once a new stable release of a defendant package is released. Additionally, reproducible builds are a strong requirement in order to securely distribute future major releases of lnd.
2016-07-23 03:52:36 +02:00
subpackages:
- bloom
- coinset
- hdkeychain
- txsort
- package: github.com/roasbeef/btcwallet
build: update glide files to pin against the master branch of roasbeef's btcwallet fork
2016-08-13 00:04:26 +02:00
version: master
add glide dependency management for fully reproducible builds This commit adds glide integration in order to make lnd builds fully reproducible. Rather than using “go get” users should now manually pull down the repo, use glide to fetch+install the dependancies, then manually install all related binaries. With this change we no longer have to chase dependancies making breaking API changes under us. We can manually update the managed dependancies once a new stable release of a defendant package is released. Additionally, reproducible builds are a strong requirement in order to securely distribute future major releases of lnd.
2016-07-23 03:52:36 +02:00
subpackages:
- chain
- waddrmgr
- wallet
- walletdb/bdb
build: update glide dependancies
2016-07-26 19:43:11 +02:00
- package: github.com/urfave/cli
version: ^1.18.0
add glide dependency management for fully reproducible builds This commit adds glide integration in order to make lnd builds fully reproducible. Rather than using “go get” users should now manually pull down the repo, use glide to fetch+install the dependancies, then manually install all related binaries. With this change we no longer have to chase dependancies making breaking API changes under us. We can manually update the managed dependancies once a new stable release of a defendant package is released. Additionally, reproducible builds are a strong requirement in order to securely distribute future major releases of lnd.
2016-07-23 03:52:36 +02:00
- package: golang.org/x/crypto
subpackages:
- hkdf
- nacl/secretbox
- ripemd160
- scrypt
- package: golang.org/x/net
subpackages:
- context
- package: google.golang.org/grpc
version: ^1.0.0
build: update the glide files to include the sphinx package and pin the routing package
2016-09-21 01:33:08 +02:00
- package: github.com/lightningnetwork/lightning-onion
glide: pin sphinx package dependency at the commit level With this commit we now pin the version of lightning-onion we build against at a particular build on the Sphinx package as the package will be modified in order to accommodate for future changes in the spec.
2017-01-17 02:41:14 +01:00
version: a527838cac5e47260fb61ed155b9b24a6d6a10cc
lnrpc: add cursory REST support to the RPC server This commit adds a REST interface to the existing gRPC server by employing a simple http proxy auto-generated from the existing protobuf files. Currently full-support for any streaming RPC’s are currently untested. In addition to auto-generating a REST proxy server, a swagger.json is also generated which allows for gRPC-like native objects with higher-level clients, and also for auto-generated documentation. Due to limitations with accepting raw byte strings as parameters, some RPC’s have been modified to take both raw-bytes and string arguments. Additionally a new RPC has been added ‘NewWitnessAddress’ since the proxy doesn’t currently support enum-based arguments. Currently the proxy server is embedded within the daemon as an active HTTP server, however we may want to package the proxy server as a separate binary in the future. Similarly, we may want to add additional configuration information which controls the optional inclusion of the REST proxy. Atm, just like the current gRPC interface, the REST API is fully unauthenticated. Before moving to an initial alpha release after making the necessary changes to meet the spec drafted in Milan, authentication of the RPC interfaces will be addressed.
2016-10-15 23:38:47 +02:00
- package: github.com/grpc-ecosystem/grpc-gateway
version: ^1.1.0
build: add aead/chacha20 and aead/poly1305 to the glide files The two new dependancies are needed for the new brontide package which implements the p2p encryption+auth.
2016-10-18 04:45:33 +02:00
- package: github.com/aead/chacha20
testing: add CT (Custom Testing) structure; create uniq point for 'lnd process errors' and 'test panic/failed errors' handling
2016-10-15 15:47:09 +02:00
- package: github.com/go-errors/errors
zpay32: create new package for encoding/decoding payment requests This commit adds a new package “zpay32”: which is used within the daemon to encode/decode payment requests. A payment request currently consists of: the public key of the payee, the payment hash to use, and finally the amount to send over the network. The encoded payment request consists of the mentioned fields concatenated to each other, a cc32 checksum is added, then the blob is finally encoded using zbas32. I call the resulting scheme “zpay32”. A number of extensions may be explored in future commits including adding a version byte, adding “hint” routing information, cryptographically signed receipts and more,
2017-01-03 00:16:57 +01:00
- package: github.com/tv42/zbase32
cmd/lncli: add ability to render graph to 'describegraph' This commit adds an ability to render the channel graph as returned by the ‘displaygraph’ command. The rendering of the graph itself is carried about the by the ‘dot’ command which eventually calls out to graphviz. Currently the graph is always saved to the same file in the local directory, but in a later commit the location of the file will be made configurable. Finally, the attributes sent to the ‘dot’ command used to render the graph are still a bit in flux. The parameters will likely be tuned once the channel graph on testnet grows a bit more.
2017-01-24 05:32:17 +01:00
- package: github.com/awalterschulze/gographviz
version: ^1.0.0
Reference in New Issue Copy Permalink