openSUSE Build Service

Overview Repositories Revisions Requests Users Attributes Meta

File rbenv.spec of Package rbenv (Revision 65c5eaa5216962d8d7317732608b44ac)

Currently displaying revision 65c5eaa5216962d8d7317732608b44ac , Show latest

Name:          rbenv
Version:       1.2.0
Release:       0
BuildArch:     noarch
License:       MIT
Group:         Development/Languages/Ruby
Url:           https://github.com/rbenv/rbenv
Summary:       Simple Ruby version Management
Source0:       https://github.com/rbenv/rbenv/archive/v%{version}.tar.gz#/%{name}-%{version}.tar.gz
# Without this patch, the two skipped tests would fail. In a Tumbleweed docker container, all tests pass, so there most likely is a BuildRequires missing.
Patch0:        skip-failing-tests.patch
%if %{undefined sle_version}
BuildRequires: bats
BuildRequires: git
%endif
Requires:      bash
Conflicts:     rvm
Recommends:    ruby-build
Recommends:    bash-completion

%description
rbenv does…

- Let you change the global Ruby version on a per-user basis.
- Provide support for per-project Ruby versions.
- Allow you to override the Ruby version with an environment variable.

In contrast with rvm, rbenv does not…

- Need to be loaded into your shell. Instead, rbenv's shim approach works by adding a directory to your $PATH.
- Override shell commands like cd. That's dangerous and error-prone.
- Have a configuration file. There's nothing to configure except which version of Ruby you want to use.
- Install Ruby. You can build and install Ruby yourself, or use ruby-build to automate the process.
- Manage gemsets. Bundler is a better way to manage application dependencies. If you have projects that are not yet using Bundler you can install the rbenv-gemset plugin.
- Require changes to Ruby libraries for compatibility. The simplicity of rbenv means as long as it's in your $PATH, nothing else needs to know about it.
- Prompt you with warnings when you switch to a project. Instead of executing arbitrary code, rbenv reads just the version name from each project. There's nothing to "trust."

%prep
%setup -q

%patch0 -p1

%build

%install
mkdir -p %{buildroot}%{_bindir}
cp libexec/* %{buildroot}%{_bindir}

mkdir -p %{buildroot}%{_datadir}/%{name}/completions
cp completions/* %{buildroot}%{_datadir}/%{name}/completions

sed -i 's|$root/completions|%{_datadir}/%{name}/completions|g' %{buildroot}%{_bindir}/rbenv-init
sed -i 's|#!/usr/bin/env bash|#!/bin/bash|g' %{buildroot}%{_bindir}/*

%check
%if %{undefined sle_version}
bats test
%endif

%files
%license LICENSE
%doc README.md
%{_bindir}/rbenv*
%dir %{_datadir}/%{name}
%{_datadir}/%{name}/*

Places

File rbenv.spec of Package rbenv (Revision 65c5eaa5216962d8d7317732608b44ac)

Places