Linux workstation

Upstream software project

rbenv

Bash completion for rbenv

About rbenv

Bash completion for rbenv

This project links 8 native package records across 4 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

rbenv repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Fedora 43: 1 package records; Fedora 44: 1 package records; openSUSE Leap 16.0: 3 package records; openSUSE Tumbleweed: 3 package records. Catalog coverage diagram, not an application screenshot.rbenv: recorded package coverageFedora 431 recordsFedora 441 recordsopenSUSE Leap 16.03 recordsopenSUSE Tumbleweed3 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
rbenv
Publisher
Not authoritatively mapped
Native package records
8
Operating systems
fedora-43, fedora-44, opensuse-leap-16-0, opensuse-tumbleweed
License expression
MIT
Metadata completeness
100/100 (not a software quality rating)
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

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

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Fedora 43

  1. rbenv

    Fedora 43 / Unspecified / source rbenv

    1.3.2-2.fc43

    Manage your app's Ruby environment

    aarch64x86_6443

Fedora 44

  1. rbenv

    Fedora 44 / Unspecified / source rbenv

    1.3.2-4.fc44

    Manage your app's Ruby environment

    aarch64noarchx86_6444

openSUSE Leap 16.0

  1. rbenv

    openSUSE Leap 16.0 / Development/Languages/Ruby / source rbenv

    1.3.0-bp160.1.11

    Simple Ruby version Management

    noarchleap-16.0
  2. rbenv-bash-completion

    openSUSE Leap 16.0 / Development/Languages/Ruby / source rbenv

    1.3.0-bp160.1.11

    Bash completion for rbenv

    noarchleap-16.0
  3. rbenv-zsh-completion

    openSUSE Leap 16.0 / Development/Languages/Ruby / source rbenv

    1.3.0-bp160.1.11

    ZSH completion for rbenv

    noarchleap-16.0

openSUSE Tumbleweed

  1. rbenv

    openSUSE Tumbleweed / Development/Languages/Ruby / source rbenv

    1.3.2-1.4

    Simple Ruby version Management

    noarchtumbleweed
  2. rbenv-bash-completion

    openSUSE Tumbleweed / Development/Languages/Ruby / source rbenv

    1.3.2-1.4

    Bash completion for rbenv

    noarchtumbleweed
  3. rbenv-zsh-completion

    openSUSE Tumbleweed / Development/Languages/Ruby / source rbenv

    1.3.2-1.4

    ZSH completion for rbenv

    noarchtumbleweed

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.

rbenv Software and Packages | OpenFactory