Metadata-Version: 1.0
Name: syseggrecipe
Version: 0.4
Summary: Syseggrecipe allows the reuse of system eggs in buildout installs
Home-page: https://github.com/nens/syseggrecipe
Author: Roland van Laar
Author-email: roland@nelen-schuurmans.nl
License: MIT
Description: Description
        ===========
        
        The buildout syseggrecipe uses system installed eggs, 
        called syseggs.
        These syseggs are used instead of installing them again during buildout.
        This is usefull for hard to compile eggs or eggs that need specific 
        development libraries.
        
        Example
        ========
        
        An example of how to use the recipe. Please note that the sysegg recipe
        must be the first buildout part.::
        
          [buildout]
          parts = sysegg
          
          [sysegg]
          recipe = syseggrecipe
          eggs =
            netCDF4
        
        To stop the buildout when not all syseggs are installed include: 
        `force-sysegg = True`.::
        
          [buildout]
          parts = sysegg
        
          [sysegg]
          recipe = syseggrecipe
          force-sysegg = true
          eggs =
            netCDF4
        
        Tests
        ======
        
        To test if all syseggs are available while `force-sysegg = true` is 
        enabled in the buildout configuration.:: 
        
          bin/buildout sysegg:force-sysegg=false install sysegg
        
        Origin
        ======
        
        This package is a fork of osc.recipe.sysegg_.
        As such it is licensed under MIT. 
        
        .. _osc.recipe.sysegg: http://pypi.python.org/pypi/osc.recipe.sysegg
        
        
        CHANGES
        =======
        
        
        0.4 (2013-09-10)
        ----------------
        
        - Back to symlinking instead of copying: some egg-info files are
          actually directories. Downside: Windows is out of the door again.
        
        
        0.3 (2013-09-10)
        ----------------
        
        - We report files that we've added to buildout now so that buildout
          automatically cleans them up for us. No more pollution in our
          develop-eggs directory!
        
        - Symlinking folders of non-egg distributions that we found in a
          system directory turned out to be a bad idea. Some distributions
          install files instead of directories (GDAL ends up as ``gdal.py``,
          for instance). We now only copy the "egg-info" files, which turns
          out to be enough for setuptools to find the distributions.
        
        - Copying (see above) instead of symlinking means it also works on
          windows again.
        
        
        0.2 (2013-09-10)
        ----------------
        
        - Fix in README for running sysegg standalone.
        
        - Distributions that aren't eggs but directories directly inside a
          ``sys.path`` directory would have the actual system folder as their
          location. This used to mean that everything in that system folder
          can erroneously be used as a system egg. Not anymore, as those
          directories are now symlinked directly instead of being used through
          a too-generic ``.egg-link`` file.
        
        - This recipe uses symlinks for the above fix, which means it doesn't
          work on windows anymore.
        
        
        0.1 (2013-02-05)
        ----------------
        
        - Patch code to allow for force-sysegg=false
        
        - Add original code from osc.recipe.sysegg.
        
        - Add buildout and setup.py.
        
        - Added readme, changes and MIT license.
        
Platform: UNKNOWN
Classifier: Framework :: Buildout
Classifier: Topic :: Software Development :: Build Tools
Classifier: Development Status :: 4 - Beta
Classifier: License :: OSI Approved :: MIT License
Classifier: Programming Language :: Python :: 2.6
Classifier: Programming Language :: Python :: 2.7
Classifier: Environment :: MacOS X
Classifier: Environment :: Console
