mirror of
https://github.com/octoleo/syncthing.git
synced 2024-11-20 11:55:18 +00:00
65aaa607ab
Change made by: - running "gvt fetch" on each of the packages mentioned in Godeps/Godeps.json - `rm -rf Godeps` - tweaking the build scripts to not mention Godeps - tweaking the build scripts to test `./lib/...`, `./cmd/...` explicitly (to avoid testing vendor) - tweaking the build scripts to not juggle GOPATH for Godeps and instead set GO15VENDOREXPERIMENT. This also results in some updated packages at the same time I bet. Building with Go 1.3 and 1.4 still *works* but won't use our vendored dependencies - the user needs to have the actual packages in their GOPATH then, which they'll get with a normal "go get". Building with Go 1.6+ will get our vendored dependencies by default even when not using our build script, which is nice. By doing this we gain some freedom in that we can pick and choose manually what to include in vendor, as it's not based on just dependency analysis of our own code. This is also a risk as we might pick up dependencies we are unaware of, as the build may work locally with those packages present in GOPATH. On the other hand the build server will detect this as it has no packages in it's GOPATH beyond what is included in the repo. Recommended tool to manage dependencies is github.com/FiloSottile/gvt.
51 lines
1.7 KiB
Markdown
51 lines
1.7 KiB
Markdown
Suture
|
|
======
|
|
|
|
[](https://travis-ci.org/thejerf/suture)
|
|
|
|
Suture provides Erlang-ish supervisor trees for Go. "Supervisor trees" ->
|
|
"sutree" -> "suture" -> holds your code together when it's trying to die.
|
|
|
|
This library has hit maturity, and isn't expected to be changed
|
|
radically. This can also be imported via gopkg.in/thejerf/suture.v1 .
|
|
|
|
It is intended to deal gracefully with the real failure cases that can
|
|
occur with supervision trees (such as burning all your CPU time endlessly
|
|
restarting dead services), while also making no unnecessary demands on the
|
|
"service" code, and providing hooks to perform adequate logging with in a
|
|
production environment.
|
|
|
|
[A blog post describing the design decisions](http://www.jerf.org/iri/post/2930)
|
|
is available.
|
|
|
|
This module is fully covered with [godoc](http://godoc.org/github.com/thejerf/suture),
|
|
including an example, usage, and everything else you might expect from a
|
|
README.md on GitHub. (DRY.)
|
|
|
|
Code Signing
|
|
------------
|
|
|
|
Starting with the commit after ac7cf8591b, I will be signing this repository
|
|
with the ["jerf" keybase account](https://keybase.io/jerf).
|
|
|
|
Aspiration
|
|
----------
|
|
|
|
One of the big wins the Erlang community has with their pervasive OTP
|
|
support is that it makes it easy for them to distribute libraries that
|
|
easily fit into the OTP paradigm. It ought to someday be considered a good
|
|
idea to distribute libraries that provide some sort of supervisor tree
|
|
functionality out of the box. It is possible to provide this functionality
|
|
without explicitly depending on the Suture library.
|
|
|
|
Changelog
|
|
---------
|
|
|
|
suture uses semantic versioning.
|
|
|
|
1. 1.0.0
|
|
* Initial release.
|
|
2. 1.0.1
|
|
* Fixed data race on the .state variable.
|
|
|