cdxsite.databrowser 2.0.1

Developers

If you’re stuck maintaining this package, note that it depends on the CDX client package. That’s all well and dandy, except that the client itself depends on PyHDF, which may look like a nice standard Python enhanced egg, but believe me, it’s not. OK, it probably is, but it depends on NumPY and HDF4, both of which are problematic.

Here’s what I ended up having to do:

1. Pick a prefix, call it $PREFIX.

2. virtualenv-2.6 –distribute –no-site-packages –prompt=cdxcrap $PREFIX

3. cd $PREFIX

4. bin/pip install numpy

5. mkdir src

6. cd src

7. curl -L ‘http://www.hdfgroup.org/ftp/HDF/HDF_Current/src/hdf-4.2.6.tar.bz2’ | tar xjf -

8. cd hdf-4.2.6

9. ./configure –prefix=$PREFIX –without-szlib –disable-fortran

10. make

11. make install

12. cd ..

13. curl -L ‘http://sourceforge.net/projects/pysclint/files/pyhdf/0.8.3/pyhdf-0.8.3.tar.gz’ | tar xzf -

14. cd pyhdf-0.8.3

15. env NOSZIP=1 INCLUDE_DIRS=$PREFIX/include LIBRARY_DIRS=$PREFIX/lib $PREFIX/bin/python2.6 setup.py install

You can then use $PREFIX/bin/python2.6 with this egg:

1. $PREFIX/bin/python2.6 bootstrap.py -d

2. bin/buildout

3. bin/test

Tests pass, so it must work!

cdxsite.databrowser Installation

Use zc.buildout and the plone.recipe.zope2instance:

• Add cdxsite.databrowser to the list of eggs to install, e.g.:

  [buildout]
  ...
  eggs =
      ...
      cdxsite.databrowser

• Tell the plone.recipe.zope2instance recipe to install a ZCML slug:

  [instance]
  recipe = plone.recipe.zope2instance
  ...
  zcml =
      cdxsite.databrowser

• Re-run buildout, e.g. with:

  $ ./bin/buildout

You can skip the ZCML slug if you are going to explicitly include the package from another package’s configure.zcml file.

Changelog

Copyright

Copyright 2008-2011 by the California Institute of Technology. ALL RIGHTS RESERVED.

The Software is owned by Caltech/JPL and is protected by United States copyright laws and applicable international treaties and/or conventions. The United States Government may have prior rights to use some or all of the Software as determined under applicable contracts and license agreements with Caltech/JPL.

This software was developed at the Jet Propulsion Laboratory, an operating division of the California Institute of Technology and is not available for use by any person, organization, or other entity without prior, specific written permission.