Update of /cvsroot/fink/dists/10.4/stable/main/finkinfo/libs/pythonmods
In directory sfp-cvs-1.v30.ch3.sourceforge.com:/tmp/cvs-serv21244/pythonmods
Added Files:
virtualenv-systempython.info
Log Message:
add virtualenv for system python to allow creating virtualenvs based on the
system python
--- NEW FILE: virtualenv-systempython.info ---
Info2: <<
Package: virtualenv-systempython%type_pkg[python]
Version: 1.9.1
Revision: 1
Homepage: http://pypi.python.org/pypi/virtualenv
Maintainer: Kurt Schwehr <goat...@users.sourceforge.net>
Type: python (2.5 2.6 2.7)
Distribution: (%type_pkg[python] = 26) 10.6, (%type_pkg[python] = 26) 10.7,
(%type_pkg[python] = 27) 10.7
BuildDepends: setuptools-tng-systempython%type_pkg[python]
Source: http://pypi.python.org/packages/source/v/virtualenv/virtualenv-%v.tar.gz
Source-MD5: 07e09df0adfca0b2d487e39a4bf2270a
CompileScript: <<
#!/bin/bash -ev
/usr/bin/python%type_raw[python] setup.py build
<<
InstallScript: <<
#!/bin/bash -ev
/usr/bin/python%type_raw[python] setup.py install --prefix=%p --root=%d \
--install-purelib=%p/Library/Python/%type_raw[python]/site-packages \
--install-platlib=%p/Library/Python/%type_raw[python]/site-packages
mv %i/bin/virtualenv %i/bin/virtualenv-systempython%type_pkg[python]
<<
PostInstScript: <<
# Add --verbose to update-alternatives for debugging
update-alternatives --verbose --install %p/bin/virtualenv
virtualenv-systempython %p/bin/virtualenv-systempython%type_pkg[python]
%type_pkg[python]
<<
PreRmScript: <<
if [ $1 != "upgrade" ]; then
update-alternatives --verbose --remove virtualenv-systempython
%p/bin/virtualenv-systempython%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).
<<
RuntimeVars: PYTHONPATH: %p/Library/Python/%type_raw[python]/site-packages
DescUsage: <<
The package sets the runtime environment variable PYTHONPATH to
%p/Library/Python/%type_raw[python]/site-packages, so that
/usr/bin/python%type_raw[python]
will find modules with a standard 'import' statement.
<<
# Info2
<<
------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
_______________________________________________
Fink-commits mailing list
Fink-commits@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.cvs
