Personal tools
You are here: Home catalog hexagonit.recipe.download
Log in


Forgot your password?
 

hexagonit.recipe.download

zc.buildout recipe for downloading and extracting packages

Current release
hexagonit.recipe.download 1.3.0-enfold

Released Feb 17, 2010

Download file Get hexagonit.recipe.download for All platforms (7.5 kB)
hexagonit.recipe.download-1.3.0-enfold.tar.gz
Download file Get hexagonit.recipe.download for All platforms (12.6 kB)
hexagonit.recipe.download-1.3.0_enfold-py2.4.egg

Project Description

Download recipe for zc.buildout

The recipe downloads packages from the net and extracts them on the filesystem. It is based on the gocept.download recipe with a few additional features.

Detailed Documentation

Supported options

The hexagonit.recipe.download recipe can be used to download and extract packages from the net. It supports the following options:

url
URL to the package that will be downloaded and extracted. The supported package formats are .tar.gz, .tar.bz2, and .zip. The value must be a full URL, e.g. http://python.org/ftp/python/2.4.4/Python-2.4.4.tgz.
strip-top-level-dir
Switch to remove the top level directory from the extracted archive. This will work only if the archive has exactly one top level directory. Accepted values are 'true' or 'false'. Defaults to 'false'.
ignore-existing
Switch to ignore existing files and/or directories. By default, the extraction process fails if there is existing files or directories matching the ones from the archive. Enabling this option will skip these files/directories from the archive. When this recipe is uninstalled the ignored files/directories will not be removed. Accepted values are 'true' or 'false'. Defaults to 'false'.
md5sum
MD5 checksum for the package file. If available the MD5 checksum of the downloaded package will be compared to this value and if the values do not match the execution of the recipe will fail.
destination
The location where the extracted contents of the package will be placed. If omitted, a directory will be created under the buildout['parts-directory'] with the name of the section using the recipe.
download-only
When set to 'true', the recipe downloads the file without trying to extract it. This is useful for downloading non-tarball files. The strip-top-level-dir option will be ignored if this option is enabled. Defaults to false.
environment-section

Name of a section that provides environment variables that will be used to update os.environ before executing the recipe.

The values of the environment variables may contain references to other existing environment variables (including themselves) in the form of Python string interpolation variables using the dictionary notation. These references will be expanded before os.environ is updated. This can be used, for example, to append to the PATH variable, e.g.:

[component]
recipe = hexagonit.recipe.cmmi
environment-section = environment

[environment]
PATH = %(PATH)s:${buildout:directory}/bin
environment

A sequence of KEY=VALUE pairs separated by newlines that define additional environment variables used to update os.environ before executing the recipe.

The semantics of this option are the same as environment-section. If both environment-section and environment are provided the values from the former will be overridden by the latter allowing per-part customization.

The recipe uses the zc.buildout Download API to perform the actual download which allows additional configuration of the download process.

By default, the recipe sets the download-cache option to ${buildout:directory}/downloads and creates the directory if necessary. This can be overridden by providing the download-cache option in your [buildout] section.

Simple example

>>> import os.path
>>> testdata = join(os.path.dirname(__file__), 'testdata')
>>> server = start_server(testdata)

In the simplest form we can download a simple package and have it extracted in the parts directory.

>>> write(sample_buildout, 'buildout.cfg',
... """
... [buildout]
... newest = false
... parts = package1
...
... [package1]
... recipe = hexagonit.recipe.download
... url = %spackage1-1.2.3-final.tar.gz
... """ % server)

Ok, let's run the buildout:

>>> print system(buildout)
Installing package1.
Downloading http://test.server/package1-1.2.3-final.tar.gz
package1: Extracting package to /sample-buildout/parts/package1

Let's take a look at the buildout parts directory now.

>>> ls(sample_buildout, 'parts')
d package1

The containing directory is named after our part name. Within this directory are the contents of the extracted package.

>>> ls(sample_buildout, 'parts', 'package1')
d package1-1.2.3-final

The package contained a single top level directory. Let's peek what's inside.

>>> ls(sample_buildout, 'parts', 'package1', 'package1-1.2.3-final')
- CHANGES.txt
- README.txt
d src

Sharing packages between buildouts

Using the download-cache option in the buildout allows you to store the downloaded packages in central location on your filesystem. Using the the same location for the download-cache in multiple buildouts will effectively share the packages between them and reduce the network traffic and storage requirements.

Let's create a directory to be used as the download cache.

>>> cache = tmpdir('cache')

And create a new buildout that sets the buildout-cache option accordingly.

>>> write(sample_buildout, 'buildout.cfg',
... """
... [buildout]
... newest = false
... parts = sharedpackage
... download-cache = %(cache)s
...
... [sharedpackage]
... recipe = hexagonit.recipe.download
... url = %(server)spackage1-1.2.3-final.tar.gz
... """ % dict(cache=cache, server=server))

Ok, let's run the buildout:

>>> print system(buildout)
Uninstalling package1.
Installing sharedpackage.
Downloading http://test.server/package1-1.2.3-final.tar.gz
sharedpackage: Extracting package to /sample-buildout/parts/sharedpackage

We can see that the package was placed under the shared container instead of the default location under the buildout directory.

>>> ls(cache)
d dist
- package1-1.2.3-final.tar.gz

MD5 checksums

The downloaded package can be verified against an MD5 checksum. This will make it easier to spot problems if the file has been changed.

If the checksum fails we get an error.

>>> write(sample_buildout, 'buildout.cfg',
... """
... [buildout]
... newest = false
... parts = package1
...
... [package1]
... recipe = hexagonit.recipe.download
... url = %spackage1-1.2.3-final.tar.gz
... md5sum = invalid
... """ % server)
>>> print system(buildout)
Uninstalling sharedpackage.
Installing package1.
While:
  Installing package1.
Error: MD5 checksum mismatch for cached download from 'http://test.server/package1-1.2.3-final.tar.gz' at '/sample-buildout/downloads/package1-1.2.3-final.tar.gz'

Using a valid checksum allows the recipe to proceed.

>>> write(sample_buildout, 'buildout.cfg',
... """
... [buildout]
... newest = false
... parts = package1
...
... [package1]
... recipe = hexagonit.recipe.download
... url = %s/package1-1.2.3-final.tar.gz
... md5sum = 821ecd681758d3fc03dcf76d3de00412
... """ % server)
>>> print system(buildout)
Installing package1.
package1: Extracting package to /sample-buildout/parts/package1

Controlling the extraction process

We can also extract the archive to any arbitrary location and have the top level directory be stripped, which is often a useful feature.

>>> tmpcontainer = tmpdir('otherplace')
>>> write(sample_buildout, 'buildout.cfg',
... """
... [buildout]
... newest = false
... parts = package1
...
... [package1]
... recipe = hexagonit.recipe.download
... url = %(server)s/package1-1.2.3-final.tar.gz
... md5sum = 821ecd681758d3fc03dcf76d3de00412
... destination = %(dest)s
... strip-top-level-dir = true
... """ % dict(server=server, dest=tmpcontainer))

Rerunning the buildout now gives us

>>> print system(buildout)
Uninstalling package1.
Installing package1.
package1: Extracting package to /otherplace

Taking a look at the extracted contents we can also see that the top-level directory has been stripped.

>>> ls(tmpcontainer)
- CHANGES.txt
- README.txt
d src

Partial extraction over existing content

By default, the recipe will fail if the destination where the package will be extracted already contains files or directories also included in the package.

>>> container = tmpdir('existing')
>>> existingdir = mkdir(container, 'src')
>>> write(sample_buildout, 'buildout.cfg',
... """
... [buildout]
... newest = false
... parts = package1
...
... [package1]
... recipe = hexagonit.recipe.download
... url = %(server)s/package1-1.2.3-final.tar.gz
... md5sum = 821ecd681758d3fc03dcf76d3de00412
... destination = %(dest)s
... strip-top-level-dir = true
... """ % dict(server=server, dest=container))

Running the buildout now will fail because of the existing src directory in the destination.

>>> print system(buildout)
Uninstalling package1.
Installing package1.
package1: Extracting package to /existing
package1: Target /existing/src already exists. Either remove it or set ``ignore-existing = true`` in your buildout.cfg to ignore existing files and directories.
While:
  Installing package1.
Error: File or directory already exists.

Setting the ignore-existing option will allow the recipe to proceed.

>>> rmdir(container)
>>> container = tmpdir('existing')
>>> existingdir = mkdir(container, 'src')
>>> write(sample_buildout, 'buildout.cfg',
... """
... [buildout]
... newest = false
... parts = package1
...
... [package1]
... recipe = hexagonit.recipe.download
... url = %(server)s/package1-1.2.3-final.tar.gz
... md5sum = 821ecd681758d3fc03dcf76d3de00412
... destination = %(dest)s
... strip-top-level-dir = true
... ignore-existing = true
... """ % dict(server=server, dest=container))
>>> print system(buildout)
Installing package1.
package1: Extracting package to /existing
package1: Ignoring existing target: /existing/src
>>> ls(container)
- CHANGES.txt
- README.txt
d src

Also note that when the recipe is uninstalled the ignored targets will not be removed as they are not part of the output of this recipe. We can verify this by running the buildout again with a different destination.

>>> write(sample_buildout, 'buildout.cfg',
... """
... [buildout]
... newest = false
... parts = package1
...
... [package1]
... recipe = hexagonit.recipe.download
... url = %(server)s/package1-1.2.3-final.tar.gz
... md5sum = 821ecd681758d3fc03dcf76d3de00412
... strip-top-level-dir = true
... ignore-existing = true
... """ % dict(server=server))
>>> print system(buildout)
Uninstalling package1.
Installing package1.
package1: Extracting package to /sample-buildout/parts/package1

Now when we look into the directory containing the previous buildout we can see that the src directory is still there but the rest of the files are gone.

>>> ls(container)
d src

Offline mode

If the buildout is run in offline mode the recipe will still work if the package is cached in the downloads directory. Otherwise the user will be informed that downloading the file is not possible in offline mode.

>>> write(sample_buildout, 'buildout.cfg',
... """
... [buildout]
... newest = false
... parts = package1
... offline = true
...
... [package1]
... recipe = hexagonit.recipe.download
... url = %(server)s/package1-1.2.3-final.tar.gz
... md5sum = 821ecd681758d3fc03dcf76d3de00412
... strip-top-level-dir = true
... """ % dict(server=server))

Let's verify that we do have a cached copy in our downloads directory.

>>> ls(sample_buildout, 'downloads')
- package1-1.2.3-final.tar.gz
>>> print system(buildout)
Uninstalling package1.
Installing package1.
package1: Extracting package to /sample-buildout/parts/package1

When we remove the file from the filesystem the recipe will not work.

>>> remove(sample_buildout, 'downloads', 'package1-1.2.3-final.tar.gz')
>>> write(sample_buildout, 'buildout.cfg',
... """
... [buildout]
... newest = false
... parts = package1
... offline = true
...
... [package1]
... recipe = hexagonit.recipe.download
... url = %(server)spackage1-1.2.3-final.tar.gz
... md5sum = 821ecd681758d3fc03dcf76d3de00412
... """ % dict(server=server))
>>> print system(buildout)
Uninstalling package1.
Installing package1.
While:
  Installing package1.
Error: Couldn't download 'http://test.server/package1-1.2.3-final.tar.gz' in offline mode.

Downloading arbitrary files

We can download any file when setting the download-only option to true. This will simply place the file in the destination directory.

>>> downloads = tmpdir('downloads')
>>> write(sample_buildout, 'buildout.cfg',
... """
... [buildout]
... newest = false
... parts = package
...
... [package]
... recipe = hexagonit.recipe.download
... url = %(server)spackage1-1.2.3-final.tar.gz
... md5sum = 821ecd681758d3fc03dcf76d3de00412
... destination = %(dest)s
... download-only = true
... """ % dict(server=server, dest=downloads))
>>> print system(buildout)
Installing package.
Downloading http://test.server/package1-1.2.3-final.tar.gz

Looking into the destination directory we can see that the file was downloaded but not extracted. Using the download-only option will work for any file regardless of the type.

>>> ls(downloads)
-  package1-1.2.3-final.tar.gz

Environment variables

Let's set some environment variables

>>> tmp = tmpdir('temp')
>>> write(sample_buildout, 'buildout.cfg',
... """
... [buildout]
... newest = false
... parts = package
...
... [environ]
... A = B
...
... [package]
... recipe = hexagonit.recipe.download
... url = %(server)spackage1-1.2.3-final.tar.gz
... md5sum = 821ecd681758d3fc03dcf76d3de00412
... download-only = true
... environment-section = environ
... environment =
...     TEMP=/a
...     TMP=/b
...     TMPDIR=/c
... """ % dict(server=server))
>>> print system(buildout)
Uninstalling package.
Installing package.
package: [ENV] A = B
package: [ENV] TEMP = /a
package: [ENV] TMP = /b
package: [ENV] TMPDIR = /c
package: Setting tempfile.tempdir to: /c

Contributors

« May 2013 »
May
MonTueWedThuFriSatSun
12345
6789101112
13141516171819
20212223242526
2728293031