Software Alternatives, Accelerators & Startups

pathogen.vim VS pkgsrc

Compare pathogen.vim VS pkgsrc and see what are their differences

pathogen.vim logo pathogen.vim

pathogen.vim: manage your runtimepath. Contribute to tpope/vim-pathogen development by creating an account on GitHub.

pkgsrc logo pkgsrc

pkgsrc is a framework for building over 17,000 open source software packages.
  • pathogen.vim Landing page
    Landing page //
    2023-10-04
  • pkgsrc Landing page
    Landing page //
    2023-06-30

pathogen.vim features and specs

  • Ease of Use
    Pathogen.vim simplifies the management of Vim plugins by allowing users to easily install, update, and remove plugins without altering Vim's core files. It requires minimal configuration.
  • Directory Structure
    It promotes a cleaner directory structure where each plugin resides in its own directory under .vim/bundle, making it easier to locate and manage individual plugins.
  • Compatibility
    Being widely adopted and time-tested, pathogen.vim is compatible with a wide range of plugins. This ensures that users can confidently use popular Vim plugins alongside it.
  • No Impact on Startup Time
    Pathogen.vim is lightweight, which means it doesn't significantly affect Vim's startup time, preserving Vim's reputation for speed and efficiency.

Possible disadvantages of pathogen.vim

  • Limited Features
    Compared to modern plugin managers like vim-plug or Vundle, pathogen.vim offers limited features, lacking built-in update mechanisms for plugins or other advanced functionalities.
  • Manual Management of Dependencies
    Pathogen.vim requires users to manually manage plugin dependencies and updates, which can become cumbersome when dealing with a large number of plugins.
  • Exclusivity of Git for Installation
    Pathogen.vim relies heavily on Git for plugin installation, which might be a limitation for users who prefer or require alternative installation methods.

pkgsrc features and specs

  • Cross-Platform Support
    pkgsrc is designed to be a portable package management system and can be used on a variety of Unix-like operating systems, including NetBSD, Solaris, Linux, and macOS. This cross-platform capability makes it a versatile tool for developers working in diverse environments.
  • Consistency Across Systems
    Using pkgsrc allows for a consistent package management experience regardless of the underlying operating system, reducing the learning curve and maintenance overhead for administrators managing multiple systems.
  • Comprehensive Package Collection
    pkgsrc offers a wide range of software packages, providing a robust collection that can meet diverse user needs from scientific libraries to web applications.
  • Quarterly Releases
    With quarterly releases, pkgsrc provides a balanced approach between stability and keeping software up to date, offering users new features regularly while maintaining reliability.
  • Flexible Build Options
    pkgsrc supports a flexible build system, allowing users to customize package builds with specific options or dependencies, tailored to their specific needs or system requirements.

Possible disadvantages of pkgsrc

  • Smaller Community
    Compared to other popular package management systems like apt (Debian/Ubuntu) or yum (RedHat/CentOS), pkgsrc has a relatively smaller community, which might affect the availability of support and community-driven improvements.
  • Potentially Older Software
    While pkgsrc maintains stable quarterly releases, it may occasionally lag behind other systems in terms of offering the very latest versions of certain software, which might not be ideal for users needing the newest features.
  • Manual Configuration
    Setting up pkgsrc might require manual interventions and configurations, which could pose a hurdle for users unfamiliar with its setup process or those who prefer more automated solutions.
  • Dependency Management
    Although pkgsrc is quite capable in dependency handling, some users may find its dependency resolution to be less automatic or seamless compared to other systems which offer more integrated solutions.
  • Performance Overhead
    Because it is designed to be cross-platform, there can be some performance overhead associated with using pkgsrc compared to native package managers that are optimized for specific operating systems.

pathogen.vim videos

No pathogen.vim videos yet. You could help us improve this page by suggesting one.

Add video

pkgsrc videos

pkgsrc on ChromeOS

More videos:

  • Review - Using pkgsrc for multi-platform deployments in heterogeneous environments, G Clifford Williams

Category Popularity

0-100% (relative to pathogen.vim and pkgsrc)
Software Development
100 100%
0% 0
Developer Tools
0 0%
100% 100
Text Editors
100 100%
0% 0
Package Manager
0 0%
100% 100

User comments

Share your experience with using pathogen.vim and pkgsrc. For example, how are they different and which one is better?
Log in or Post with

Social recommendations and mentions

Based on our record, pkgsrc should be more popular than pathogen.vim. It has been mentiond 11 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.

pathogen.vim mentions (6)

  • Any Suggestions Apart from vscode for Terraform ?
    The person who mentored me the most when I was getting started with Terraform used VIM with pathogen but honestly this isn't a great idea unless you're really invested in a VIM workflow. Source: about 3 years ago
  • Vim or Emacs?
    I am a bit confused. What has this anything to do with your original question? vim-pathogen is for Vim editor itself, not for PyCharm. I don't know much about MacOS, so not sure how to help. Did you try the installation steps at https://github.com/tpope/vim-pathogen ? Source: over 3 years ago
  • Usage of 'after/ftplugin' directory for filetype-specific configuration
    Back in the old(ish) days of Vim, usage of tpope/vim-pathogen to manipulate runtimepath was a popular way to install plugins. As it got update 9 days ago, it might be still used by some. Source: almost 4 years ago
  • Vim: NERDTree
    To install any plugin using Pathogen plugin manager, you need to configure PAthogen in your vimrc if you have not done it already. You can find the installation docs on Pathogen.vim. After Pathogen has been configured in your vimrc, you can clone the git repository of that plugin into your local machine and then activate it using Pathogen. - Source: dev.to / almost 5 years ago
  • Recommendations for "Standard, Modern Vim Config"?
    Bundles, Plugins, and Packages. Oh my! - Vim plugin management have gone through many "best practices". vim-pathogen, Vundle, vim-plug, and Vim 8's :packadd. At any given time I am certain the community would say one of these is "modern" or at the least some sort of standard. Source: about 5 years ago
View more

pkgsrc mentions (11)

  • Debian isn't waiting for 2038 to blow up, switches to 64-bit time for everything
    > Most open source software packages are also compiled for BSD variants, they switched to 64 bit time_t a long time ago and reported back upstream any problems. * NetBSD in 2012: https://www.netbsd.org/releases/formal-6/NetBSD-6.0.html * OpenBSD in 2014: http://www.openbsd.org/55.html For packaging, NetBSD uses their (multi-platform) Pkgsrc, which has 29,000 packages, which probably covers a large swath of... - Source: Hacker News / 12 months ago
  • Our Audit of Homebrew
    > https://pkgsrc.smartos.org/install-on-macos/ Note that Pkgsrc is a NetBSD-derived project. * https://pkgsrc.org The Joyent folks leveraged it to allow their customers, who were perhaps not as familiar with Solaris/SmartOS, a larger pool of packages. Pkgsrc was running on Solaris before Joyent, Joyent built on top of it. - Source: Hacker News / almost 2 years ago
  • Show HN: Brioche โ€“ A new Nix-like package manager
    Https://pkgsrc.org/ from netbsd runs on many systems. - Source: Hacker News / about 2 years ago
  • Installing packages without an internet connection?
    It seems according to pkgsrc.org that pkgin might follow the PKG_PATH environment variable. You're supposed to set PKG_PATH="http://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/$(uname -p)/$(uname -r|cut -f '1 2' -d.)/All/", and according to uname(1), -p gives the processor architecture and -r gives the operating system [kernel] release. Source: over 3 years ago
  • pkgsrc.se is no more :(
    It seems like pkgsrc.org hasnโ€™t got the news yet. Source: over 3 years ago
View more

What are some alternatives?

When comparing pathogen.vim and pkgsrc, you can also consider the following products

Vim-Plug - :hibiscus: Minimalist Vim Plugin Manager. Contribute to junegunn/vim-plug development by creating an account on GitHub.

Conda - Binary package manager with support for environments.

ale - Asynchronous Lint Engine

Homebrew - The missing package manager for macOS

Vim Awesome - Awesome Vim plugins from across the universe

Yay - Yay is an AUR helper written in go, based on the design of yaourt, apacman and pacaur.