Update of /cvsroot/fink/dists/10.4/unstable/main/finkinfo/libs/pythonmods
In directory vz-cvs-3.sog:/tmp/cvs-serv7689
Added Files:
virtualenv-py.info
Log Message:
initial commit with version 1.6.1
--- NEW FILE: virtualenv-py.info ---
Info2: <<
Package: virtualenv-py%type_pkg[python]
Version: 1.6.1
Revision: 1
Homepage: http://pypi.python.org/pypi/virtualenv
Maintainer: Kurt Schwehr <goat...@users.sourceforge.net>
Type: python (2.7)
Depends: python%type_pkg[python]
BuildDepends: distribute-py%type_pkg[python]
Source: http://pypi.python.org/packages/source/v/virtualenv/virtualenv-%v.tar.gz
Source-MD5: 1a475df2219457b6b4febb9fe595d915
CompileScript: <<
#!/bin/bash -ev
python%type_raw[python] setup.py build
<<
InstallScript: <<
#!/bin/bash -ev
python%type_raw[python] setup.py install --root=%d
mv %i/bin/virtualenv %i/bin/virtualenv-py%type_pkg[python]
<<
PostInstScript: <<
# Add --verbose to update-alternatives for debugging
update-alternatives --verbose --install %p/bin/virtualenv virtualenv-py
%p/bin/virtualenv-py%type_pkg[python] %type_pkg[python]
<<
PreRmScript: <<
if [ $1 != "upgrade" ]; then
update-alternatives --verbose --remove virtualenv-py
%p/bin/virtualenv-py%type_pkg[python]
fi
<<
License: BSD
Description: Virtual Python Environment builder
DescDetail: <<
virtualenv is a tool to create isolated Python environments.
The basic problem being addressed is one of dependencies and versions,
and indirectly permissions. Imagine you have an application that needs
version 1 of LibFoo, but another application requires version 2. How
can you use both these applications? If you install everything into
/usr/lib/python2.7/site-packages (or whatever your platform's standard
location is), it's easy to end up in a situation where you
unintentionally upgrade an application that shouldn't be upgraded.
Or more generally, what if you want to install an application and
leave it be? If an application works, any change in its libraries or
the versions of those libraries can break the application.
Also, what if you can't install packages into the global site-packages
directory? For instance, on a shared host.
In all these cases, virtualenv can help you. It creates an environment
that has its own installation directories, that doesn't share
libraries with other virtualenv environments (and optionally doesn't
access the globally installed libraries either).
<<
# Info2
<<
------------------------------------------------------------------------------
AppSumo Presents a FREE Video for the SourceForge Community by Eric
Ries, the creator of the Lean Startup Methodology on "Lean Startup
Secrets Revealed." This video shows you how to validate your ideas,
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
_______________________________________________
Fink-commits mailing list
Fink-commits@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.cvs
