Upstream software project

vim-pathogen

Manage your runtimepath

About vim-pathogen

Manage your runtimepath

This project links 2 native package records across 2 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

vim-pathogen repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Fedora 43: 1 package records; Fedora 44: 1 package records. Catalog coverage diagram, not an application screenshot.vim-pathogen: recorded package coverageFedora 431 recordsFedora 441 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
vim-pathogen
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
fedora-43, fedora-44
License expression
Vim
Source repository
Open source repository

Source-reported description

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

Manage your 'runtimepath' with ease. In practical terms, pathogen.vim makes it super easy to install plugins and runtime files in their own private directories. For new users, I recommend using Vim's built-in package management instead: :help packages

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. Package vim-pathogen

    43 (Fedora 43) (Unspecified): Manage your runtimepath

    2.4-12.20220824gitac4dd94.16.fc43: noarch

    Source: vim-pathogen

Fedora 44

  1. Package vim-pathogen

    44 (Fedora 44) (Unspecified): Manage your runtimepath

    2.4-12.20220824gitac4dd94.17.fc44: noarch

    Source: vim-pathogen

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.