File python3-virtualenv.spec of Package python3-virtualenv

# spec file for package python3-virtualenv
# Copyright (c) 2015 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

Name:           python3-virtualenv
Version:        13.1.2
Release:        0
Summary:        Virtual Python Environment builder
License:        MIT
Group:          Development/Languages/Python
BuildRoot:      %{_tmppath}/%{name}-%{version}-build
BuildRequires:  python3-devel
BuildRequires:  python3-setuptools
%if 0%{?suse_version} <= 1310
# pip is built-in for python 3.4
BuildRequires:  python3-pip
Requires:       python3-pip
Requires:       python3-setuptools
Requires(post): update-alternatives
Requires(postun): update-alternatives
BuildArch:      noarch

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).

%setup -q -n virtualenv-%{version}

python3 build

python3 install --prefix=%{_prefix} --root=%{buildroot}
# Remove script copy and replace with symlink to please u-a:
rm %{buildroot}%{_bindir}/virtualenv
ln -s %{_bindir}/virtualenv-%{py3_ver} %{buildroot}%{_bindir}/virtualenv

# Since /usr/bin/virtualenv became ghosted to be used with update-alternatives, we have to
# get rid of the old binary resulting from the non-update-alternativies-ified package:
[ -h %{_bindir}/virtualenv ] || rm -f %{_bindir}/virtualenv

update-alternatives \
    --install %{_bindir}/virtualenv virtualenv %{_bindir}/virtualenv-%{py3_ver} 30

if [ $1 -eq 0 ] ; then
    update-alternatives --remove virtualenv %{_bindir}/virtualenv-%{py3_ver}

%doc LICENSE.txt README.rst
%ghost %{_bindir}/virtualenv
%if 0%{?suse_version} >= 1230
%ghost %{_sysconfdir}/alternatives/virtualenv