otherwise the build process doesn't pick up correct versions

The miniconda installer creates the correct shebang line no problem
but conda update encounters long shebang lines and decides that they
are dangerous, so it silently replaces a "long" (≥128 bytes) path to
`python` with `/usr/bin/env python`. What could go wrong?!? This works
around that behavior by using a 16-byte "slug" in package/version
paths instead of using the full "$uuid/$sha1" string, which, to be
fair, is an excessive 77 characters in the middle of paths.

The issue was that Conda looks for long shebang lines (>127) and
silently replaces the or

character and string concatenation

otherwise the SHA package would have to be internalized

when the build takes a while, you can tail the file to see what's up

…ject packages

This allows Pkg3 loading to work even if it's loaded with `include`
instead of by being on the `LOAD_PATH` and running `using Pkg3`.

Support more forms of at-nospecialize.

remove precompile from internalized toml

add information I was missing when installing and remove remark about precompilation, which doesn't seem to be true anymore.

no precompilation remark, add pkg3 clone, pkg dir

enable precompilation for Pkg3

#24)

Asynchronously install packages

fix not printing already existing packages

* Add (sp)diagm pair constructors

…` from `UniformScaling` (#412)

* Add constructors for `Matrix{T}` and `SparseMatrixCSC{T}` from `UniformScaling`

* Add constructors for `Array{T}` from `UniformScaling`

* Add Compat.Dates for standard library Dates

* Refactor deprecated parametic syntax

Select libgit2 when tarball download fails

show pkg name on resolution failure

make a basic functional API and add some very basic tests

add preview mode

add test for pkg name in resolution failure

bump TOML

fixup v0.7

Upgrade Pkg3 and ext dependencies to 0.7

…ialized (#417)

Compat.Base64

This reverts commit 5ab47d1 due to
method ambiguities.

add at-compat for finalizer instead

at-compat finalizer

Revert function first finalizers due to ambiguities

* implement "garbage collection"

Computes the dependency graph subset induced by the requirements
after filter_versions has propagated the implicit requirements,
rather than before, which ensures that only the parts reachable
from some requirement are kept. In practice, it removes many more
useless parts of the graph.

(Plus other tiny improvements.)

Fixes the rare condition where two packages were
being decimated at once in mutually inconsistent
versions.

Bring in some functions from Base which are useful
in preparation for the cloning functionality.
They (and a few more) are also needed for
Resolve.sanity_check to work.

Also import tests for resolve.

* update registries on up

* no longer special case branch

Solver fixes, tests, etc.

* force explicit init using `init` for local env

* remove try catch, other small fixes

exit pkg repl mode with ^C

Make sure nothing beyond patch gets to Pkg2
by crudely using asserts.

Also normalize the VersionSpec in the constructor.
Also allow '*' as an extreme in VersionSpec string specification.
This is in preparation for the switch VersionSet->VersionSpec.

And some ugly reoarganization of the code.
This is in preparation for the switch VersionSet->VersionSpec