2004-04-21 17:54:05 +03:00
|
|
|
#! @shell@ -e
|
2003-08-15 13:13:41 +03:00
|
|
|
|
2004-04-21 17:54:05 +03:00
|
|
|
url=$1
|
2004-12-13 15:35:36 +02:00
|
|
|
hash=$2
|
2003-08-15 13:13:41 +03:00
|
|
|
|
* Removed the `id' attribute hack.
* Formalise the notion of fixed-output derivations, i.e., derivations
for which a cryptographic hash of the output is known in advance.
Changes to such derivations should not propagate upwards through the
dependency graph. Previously this was done by specifying the hash
component of the output path through the `id' attribute, but this is
insecure since you can lie about it (i.e., you can specify any hash
and then produce a completely different output). Now the
responsibility for checking the output is moved from the builder to
Nix itself.
A fixed-output derivation can be created by specifying the
`outputHash' and `outputHashAlgo' attributes, the latter taking
values `md5', `sha1', and `sha256', and the former specifying the
actual hash in hexadecimal or in base-32 (auto-detected by looking
at the length of the attribute value). MD5 is included for
compatibility but should be considered deprecated.
* Removed the `drvPath' pseudo-attribute in derivation results. It's
no longer necessary.
* Cleaned up the support for multiple output paths in derivation store
expressions. Each output now has a unique identifier (e.g., `out',
`devel', `docs'). Previously there was no way to tell output paths
apart at the store expression level.
* `nix-hash' now has a flag `--base32' to specify that the hash should
be printed in base-32 notation.
* `fetchurl' accepts parameters `sha256' and `sha1' in addition to
`md5'.
* `nix-prefetch-url' now prints out a SHA-1 hash in base-32. (TODO: a
flag to specify the hash.)
2005-01-17 18:55:19 +02:00
|
|
|
hashType="sha1"
|
|
|
|
|
2004-04-21 17:54:05 +03:00
|
|
|
if test -z "$url"; then
|
|
|
|
echo "syntax: nix-prefetch-url URL" >&2
|
|
|
|
exit 1
|
|
|
|
fi
|
2003-08-15 13:13:41 +03:00
|
|
|
|
2004-12-13 15:35:36 +02:00
|
|
|
# Determine the hash, unless it was given.
|
|
|
|
if test -z "$hash"; then
|
2003-08-15 13:13:41 +03:00
|
|
|
|
2004-12-13 15:35:36 +02:00
|
|
|
# !!! race
|
|
|
|
tmpPath1=@storedir@/nix-prefetch-url-$$
|
|
|
|
|
|
|
|
# Test whether we have write permission in the store. If not,
|
|
|
|
# fetch to /tmp and don't copy to the store. This is a hack to
|
|
|
|
# make this script at least work somewhat in setuid installations.
|
|
|
|
if ! touch $tmpPath1 2> /dev/null; then
|
|
|
|
echo "(cannot write to the store, result won't be cached)" >&2
|
|
|
|
dummyMode=1
|
|
|
|
tmpPath1=/tmp/nix-prefetch-url-$$ # !!! security?
|
|
|
|
fi
|
|
|
|
|
|
|
|
# Perform the checkout.
|
|
|
|
@curl@ --fail --location --max-redirs 20 "$url" > $tmpPath1
|
2004-10-20 17:40:54 +03:00
|
|
|
|
2004-12-13 15:35:36 +02:00
|
|
|
# Compute the hash.
|
* Removed the `id' attribute hack.
* Formalise the notion of fixed-output derivations, i.e., derivations
for which a cryptographic hash of the output is known in advance.
Changes to such derivations should not propagate upwards through the
dependency graph. Previously this was done by specifying the hash
component of the output path through the `id' attribute, but this is
insecure since you can lie about it (i.e., you can specify any hash
and then produce a completely different output). Now the
responsibility for checking the output is moved from the builder to
Nix itself.
A fixed-output derivation can be created by specifying the
`outputHash' and `outputHashAlgo' attributes, the latter taking
values `md5', `sha1', and `sha256', and the former specifying the
actual hash in hexadecimal or in base-32 (auto-detected by looking
at the length of the attribute value). MD5 is included for
compatibility but should be considered deprecated.
* Removed the `drvPath' pseudo-attribute in derivation results. It's
no longer necessary.
* Cleaned up the support for multiple output paths in derivation store
expressions. Each output now has a unique identifier (e.g., `out',
`devel', `docs'). Previously there was no way to tell output paths
apart at the store expression level.
* `nix-hash' now has a flag `--base32' to specify that the hash should
be printed in base-32 notation.
* `fetchurl' accepts parameters `sha256' and `sha1' in addition to
`md5'.
* `nix-prefetch-url' now prints out a SHA-1 hash in base-32. (TODO: a
flag to specify the hash.)
2005-01-17 18:55:19 +02:00
|
|
|
hash=$(@bindir@/nix-hash --base32 --type "$hashType" --flat $tmpPath1)
|
2004-12-13 15:35:36 +02:00
|
|
|
if ! test -n "$QUIET"; then echo "hash is $hash" >&2; fi
|
2003-08-15 13:13:41 +03:00
|
|
|
|
2004-12-13 15:35:36 +02:00
|
|
|
# Rename it so that the fetchurl builder can find it.
|
|
|
|
if test "$dummyMode" != 1; then
|
|
|
|
tmpPath2=@storedir@/nix-prefetch-url-$hash
|
|
|
|
test -e $tmpPath2 || mv $tmpPath1 $tmpPath2 # !!! race
|
|
|
|
fi
|
2003-08-15 13:13:41 +03:00
|
|
|
|
2004-10-20 17:40:54 +03:00
|
|
|
fi
|
2003-08-15 13:13:41 +03:00
|
|
|
|
2004-10-20 17:40:54 +03:00
|
|
|
# Create a Nix expression that does a fetchurl.
|
2004-04-21 17:54:05 +03:00
|
|
|
storeExpr=$( \
|
2004-10-20 17:40:54 +03:00
|
|
|
echo "(import @datadir@/nix/corepkgs/fetchurl) \
|
* Removed the `id' attribute hack.
* Formalise the notion of fixed-output derivations, i.e., derivations
for which a cryptographic hash of the output is known in advance.
Changes to such derivations should not propagate upwards through the
dependency graph. Previously this was done by specifying the hash
component of the output path through the `id' attribute, but this is
insecure since you can lie about it (i.e., you can specify any hash
and then produce a completely different output). Now the
responsibility for checking the output is moved from the builder to
Nix itself.
A fixed-output derivation can be created by specifying the
`outputHash' and `outputHashAlgo' attributes, the latter taking
values `md5', `sha1', and `sha256', and the former specifying the
actual hash in hexadecimal or in base-32 (auto-detected by looking
at the length of the attribute value). MD5 is included for
compatibility but should be considered deprecated.
* Removed the `drvPath' pseudo-attribute in derivation results. It's
no longer necessary.
* Cleaned up the support for multiple output paths in derivation store
expressions. Each output now has a unique identifier (e.g., `out',
`devel', `docs'). Previously there was no way to tell output paths
apart at the store expression level.
* `nix-hash' now has a flag `--base32' to specify that the hash should
be printed in base-32 notation.
* `fetchurl' accepts parameters `sha256' and `sha1' in addition to
`md5'.
* `nix-prefetch-url' now prints out a SHA-1 hash in base-32. (TODO: a
flag to specify the hash.)
2005-01-17 18:55:19 +02:00
|
|
|
{url = $url; outputHashAlgo = \"$hashType\"; outputHash = \"$hash\"; system = \"@system@\";}" \
|
2004-10-20 17:40:54 +03:00
|
|
|
| @bindir@/nix-instantiate -)
|
2003-08-15 13:13:41 +03:00
|
|
|
|
* Removed the `id' attribute hack.
* Formalise the notion of fixed-output derivations, i.e., derivations
for which a cryptographic hash of the output is known in advance.
Changes to such derivations should not propagate upwards through the
dependency graph. Previously this was done by specifying the hash
component of the output path through the `id' attribute, but this is
insecure since you can lie about it (i.e., you can specify any hash
and then produce a completely different output). Now the
responsibility for checking the output is moved from the builder to
Nix itself.
A fixed-output derivation can be created by specifying the
`outputHash' and `outputHashAlgo' attributes, the latter taking
values `md5', `sha1', and `sha256', and the former specifying the
actual hash in hexadecimal or in base-32 (auto-detected by looking
at the length of the attribute value). MD5 is included for
compatibility but should be considered deprecated.
* Removed the `drvPath' pseudo-attribute in derivation results. It's
no longer necessary.
* Cleaned up the support for multiple output paths in derivation store
expressions. Each output now has a unique identifier (e.g., `out',
`devel', `docs'). Previously there was no way to tell output paths
apart at the store expression level.
* `nix-hash' now has a flag `--base32' to specify that the hash should
be printed in base-32 notation.
* `fetchurl' accepts parameters `sha256' and `sha1' in addition to
`md5'.
* `nix-prefetch-url' now prints out a SHA-1 hash in base-32. (TODO: a
flag to specify the hash.)
2005-01-17 18:55:19 +02:00
|
|
|
echo "$storeExpr"
|
|
|
|
|
2004-04-21 17:54:05 +03:00
|
|
|
# Realise it.
|
2004-06-21 12:51:23 +03:00
|
|
|
finalPath=$(@bindir@/nix-store -qnB --force-realise $storeExpr)
|
2004-10-20 17:40:54 +03:00
|
|
|
|
2004-12-13 15:35:36 +02:00
|
|
|
if ! test -n "$QUIET"; then echo "path is $finalPath" >&2; fi
|
2003-11-22 20:45:56 +02:00
|
|
|
|
2004-12-20 16:57:03 +02:00
|
|
|
if test -n "$tmpPath1" -o -n "$tmpPath2"; then
|
|
|
|
rm -rf $tmpPath1 $tmpPath2 || true
|
|
|
|
fi
|
2003-08-15 13:13:41 +03:00
|
|
|
|
2004-04-21 17:54:05 +03:00
|
|
|
echo $hash
|
2004-06-21 12:51:23 +03:00
|
|
|
|
|
|
|
if test -n "$PRINT_PATH"; then
|
|
|
|
echo $finalPath
|
|
|
|
fi
|