
Upstream software project
vagrant
Vagrant bash autocompletion
About vagrant
Vagrant bash autocompletion
This project links 5 native package records across 1 recorded operating-system release. 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
Project identity
- Project
- vagrant
- Publisher
- Not authoritatively mapped
- Native package records
- 5
- Operating systems
- opensuse-leap-15-6
- License expression
- MIT
- Metadata completeness
- 100/100 (not a software quality rating)
- Homepage
- Visit upstream site
- Source repository
- Open source repository
Source-reported description
The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.
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.
openSUSE Leap 15.6
- vagrant2.2.18-bp156.5.1
openSUSE Leap 15.6 / Development/Languages/Ruby / source vagrant
Tool for building and distributing virtualized development environments
aarch64ppc64les390xx86_64leap-15.6 - vagrant-bash-completion2.2.18-bp156.5.1
openSUSE Leap 15.6 / Development/Languages/Ruby / source vagrant
Vagrant bash autocompletion
noarchleap-15.6 - vagrant-doc2.2.18-bp156.5.1
openSUSE Leap 15.6 / Documentation/HTML / source vagrant
Documentation for Vagrant
noarchleap-15.6 - vagrant-emacs2.2.18-bp156.5.1
openSUSE Leap 15.6 / Development/Languages/Ruby / source vagrant
Vagrantfile syntax files for the emacs editor
noarchleap-15.6 - vagrant-vim2.2.18-bp156.5.1
openSUSE Leap 15.6 / Development/Languages/Ruby / source vagrant
Vagrantfile syntax files for the vim editor
noarchleap-15.6
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.