minio server simplified its build system, this
change borrows the same technique to `mc` as well.
This PR fixes build messages and overall behavior
of our builds on travis and appveyor.
Two Makefile options are
- make release
- make experimental
Currently supported OS and arch -
- linux/386
- linux/amd64
- linux/arm
- windows/386
- windows/amd64
- darwin/amd64
This vendorization uses the new set of API changes which
we are brought in.
With this new change Bucket regions are handled transparently
without any region lookup or local map. This makes overall code
seamless and easy to use.
Fixes - #1541 (cp corruption while uploading large files to s3)
Fixes - #1542 (cp checkCopySyntax failed)
Fixes - #1537 (regions will be handled seamelessly now for all buckets)
Fixes - #1538 (fixes access control policy for google cloud storage)
Fixes - #1547 (session resume completes without copying all the files)
Fixes - #1559 (poor network connectivity, causes timing out)
By default binary built through 'go get github.com/minio/mc'. Will be
considered UNOFFICIAL.GOGET with not versioning, 'go get' binaries
cannot use 'mc update' functionality.
First reasoning towards this is - go build tools have no way to specifying
versions and releases unlike `npm`. For this reason alone we have to
differentiate OFFICIAL and UNOFFICIAL.
Now a 'make' will build appropriate binaries, while 'go get' becomes UNOFFICIAL.
- over the course of a project history every maintainer needs to update
its dependency packages, the problem essentially with godep is manipulating
GOPATH - this manipulation leads to static objects created at different locations
which end up conflicting with the overall functionality of golang.
This also leads to broken builds on many platforms. There is no easier way out of
this other than asking users to do 'godep restore' all the time which perhaps as
a practice doesn't sound clean, also has its own set of problems.
- govendor on the other hand is a right tool but a stop gap tool until we wait for
golangs official 1.5 version which fixes this vendoring issue once and for all.
- govendor makes sure that the import paths are re-written instead of manipulating
GOPATH.
This has advantages
- no more compiled objects being referenced in GOPATH and build time GOPATH
manging which leads to conflicts.
- proper import paths referencing the exact package a project is dependent on.
govendor is simple and provides the minimal necessary tooling to achieve this.
For now this is the right solution.
