kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/py-virtualenv/Makefile

19 lines
543 B
Makefile
Raw Normal View History

Update to 1.11.6: 1.11.6 (2014-05-16) ~~~~~~~~~~~~~~~~~~~ * Updated setuptools to 3.6 * Updated pip to 1.5.6
2014-05-20 10:49:26 +02:00
# $NetBSD: Makefile,v 1.12 2014/05/20 08:49:26 wiz Exp $
Import py-virtualenv-1.8.2 as devel/py-virtualenv. 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).
2012-10-07 00:23:22 +02:00
Update to 1.11.6: 1.11.6 (2014-05-16) ~~~~~~~~~~~~~~~~~~~ * Updated setuptools to 3.6 * Updated pip to 1.5.6
2014-05-20 10:49:26 +02:00
DISTNAME= virtualenv-1.11.6
Import py-virtualenv-1.8.2 as devel/py-virtualenv. 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).
2012-10-07 00:23:22 +02:00
PKGNAME= ${PYPKGPREFIX}-${DISTNAME}
CATEGORIES= devel python
MASTER_SITES= http://pypi.python.org/packages/source/v/virtualenv/
MAINTAINER= pkgsrc-users@NetBSD.org
HOMEPAGE= http://pypi.python.org/pypi/virtualenv
COMMENT= Virtual Python Environment builder
LICENSE= mit
PLIST_SUBST+= PYVERSSUFFIX=${PYVERSSUFFIX}
REPLACE_PYTHON= virtualenv.py
.include "../../lang/python/application.mk"
.include "../../lang/python/egg.mk"
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink