forked from pool/python-virtualenv
9f9d5f8bdd
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-virtualenv?expand=0&rev=57
85 lines
2.9 KiB
RPMSpec
85 lines
2.9 KiB
RPMSpec
#
|
|
# spec file for package python-virtualenv
|
|
#
|
|
# Copyright (c) 2018 SUSE LINUX GmbH, Nuernberg, Germany.
|
|
#
|
|
# All modifications and additions to the file contributed by third parties
|
|
# remain the property of their copyright owners, unless otherwise agreed
|
|
# upon. The license for this file, and modifications and additions to the
|
|
# file, is the same license as for the pristine package itself (unless the
|
|
# license for the pristine package is not an Open Source License, in which
|
|
# case the license is the MIT License). An "Open Source License" is a
|
|
# license that conforms to the Open Source Definition (Version 1.9)
|
|
# published by the Open Source Initiative.
|
|
|
|
# Please submit bugfixes or comments via http://bugs.opensuse.org/
|
|
#
|
|
|
|
|
|
%{?!python_module:%define python_module() python-%{**} python3-%{**}}
|
|
Name: python-virtualenv
|
|
Version: 15.1.0
|
|
Release: 0
|
|
Url: http://www.virtualenv.org/
|
|
Summary: Virtual Python Environment builder
|
|
License: MIT
|
|
Group: Development/Languages/Python
|
|
Source: https://pypi.io/packages/source/v/virtualenv/virtualenv-%{version}.tar.gz
|
|
BuildRoot: %{_tmppath}/%{name}-%{version}-build
|
|
BuildRequires: %{python_module devel}
|
|
BuildRequires: %{python_module setuptools}
|
|
BuildRequires: python-rpm-macros
|
|
Requires: python
|
|
Requires(post): update-alternatives
|
|
Requires(postun): update-alternatives
|
|
BuildArch: noarch
|
|
|
|
%python_subpackages
|
|
|
|
%description
|
|
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.4/site-packages (or whatever your platforms standard location
|
|
is), its easy to end up in a situation where you unintentionally upgrade an
|
|
application that shouldnt 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 cant 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 doesnt share libraries with other
|
|
virtualenv environments (and optionally doesnt use the globally installed
|
|
libraries either).
|
|
|
|
%prep
|
|
%setup -q -n virtualenv-%{version}
|
|
|
|
%build
|
|
%python_build
|
|
|
|
%install
|
|
%python_install
|
|
%python_clone -a %{buildroot}%{_bindir}/virtualenv
|
|
|
|
%post
|
|
%python_install_alternative virtualenv
|
|
|
|
%postun
|
|
%python_uninstall_alternative virtualenv
|
|
|
|
%files %python_files
|
|
%defattr(-,root,root,-)
|
|
%doc LICENSE.txt README.rst
|
|
%{python_sitelib}/virtualenv*
|
|
%python_alternative %{_bindir}/virtualenv
|
|
%pycache_only %{python_sitelib}/__pycache__
|
|
|
|
%changelog
|