Andrey Smirnov 7bad358408 Local package pool and local publishing rewritten with new constraints ...

Local package pool now implements more generic package pool API.
The base idea is to never expose full paths to files, so that other
kinds of package pools (e.g. package pool in S3) could be used to implement
the same interface.

Files get into the pool only using `Import` method. `Import` method is
now more smart, it supports moving files into the pool, it can detect if
files reside on the same filesystem and use hardlinking instead of copying.
This will make direct mirror downloads still as fast as they were with previous
version which was performing download directly to package pool.

New package pool doesn't have two things implemented yet:

1. New file placement according to SHA256 or other configured hash

2. Calculate at least SHA256/MD5 for each imported files.
MD5 would be required for S3/Swift publishing

2017-04-26 23:17:03 +03:00

..

files_test.go

Upgrade gocheck

2014-11-05 13:27:15 -06:00

files.go

Refactor Repository: split into PackagePool and PublishedStorage.

2014-02-19 12:03:01 +04:00

package_pool_test.go

Local package pool and local publishing rewritten with new constraints

2017-04-26 23:17:03 +03:00

package_pool.go

Local package pool and local publishing rewritten with new constraints

2017-04-26 23:17:03 +03:00

public_test.go

Local package pool and local publishing rewritten with new constraints

2017-04-26 23:17:03 +03:00

public.go

Local package pool and local publishing rewritten with new constraints

2017-04-26 23:17:03 +03:00