Best Package Managers in Germany - Page 2

A decentralized cross-platform software installation system. Works on Linux, Windows and macOS. Fully open-source. Run apps with a single click. Run applications without having to install them first. Control everything from a command line or graphical interface. You control your own computer. You don't have to guess what happens during installation. Mix and match stable and experimental apps on a single system. Anyone can distribute software. Create one package that works on multiple platforms. Publish on any static web host; no central point of control. With dependency handling and automatic updates. Security is central. Installing an app doesn't grant it administrator access. Digital signatures are always checked before new software is run. Apps can share libraries without having to trust each other. Adds automatic self-updating, staged rollouts and various improvements to desktop integration.

Installing, patching, and removing software packages on Linux machines is one of the common tasks every sysadmin has to do. Here is how to get started with Linux package management in Linux Red Hat-based distributions (distros). Package management is a method of installing, updating, removing, and keeping track of software updates from specific repositories (repos) in the Linux system. Linux distros often use different package management tools. Red Hat-based distros use RPM (RPM Package Manager) and YUM/DNF (Yellow Dog Updater, Modified/Dandified YUM). YUM is the primary package management tool for installing, updating, removing and managing software packages in Red Hat Enterprise Linux. YUM performs dependency resolution when installing, updating, and removing software packages. YUM can manage packages from installed repositories in the system or from .rpm packages. There are many options and commands available to use with YUM.

The RPM Package Manager (RPM) is a powerful package management system capable of building computer software from the source into easily distributable packages; installing, updating, and uninstalling packaged software; querying detailed information about the packaged software, whether installed or not; and verifying the integrity of packaged software and resulting software installation. The package’s metadata is stored in the RPM header. The header is a binary data structure that stores single pieces of data in tags. Each tag has a pre-defined meaning and data type. These are not stored in the header itself but need to be known by the code reading the header. In the header, the tags are only referred to by their number. Each tag is either of a plain scalar type or is an array of one of these types. While not enforced by the type system the RPM code assumes that tags belonging together have the same number of entries.

WPKG is an automated software deployment, upgrade, and removal program for Windows. It can be used to push/pull software packages, such as Service Packs, hotfixes, or program installations from a central server (for example, Samba or Active Directory) to a number of workstations. It can run as a service to install the software in the background (silent install), without user interaction. It can install MSI, InstallShield, PackagefortheWeb, Inno Setup, Nullsoft, other software installers or .exe packages, .bat and .cmd scripts, and similar, no more repackaging to perform software installation. WPKG is open-source software. WPKG can add great value to your Samba or Active Directory setup, as it allows you to perform software installation, updates, removal, etc. on your workstations. It is also possible to execute custom scripts on your workstations, like synchronizing time, setting printers, changing permissions, or adding registry entries.

Package manager and build system for Fortran. There are already many packages available for use with fpm, providing an easily accessible and rich ecosystem of general-purpose and high-performance code. Fortran Package Manager (fpm) is a package manager and build system for Fortran. Its key goal is to improve the user experience of Fortran programmers. It does so by making it easier to build your Fortran program or library, run the executables, tests, and examples, and distribute it as a dependency to other Fortran projects. Fpm’s user interface is modeled after Rust’s Cargo. Its long-term vision is to nurture and grow the ecosystem of modern Fortran applications and libraries. The Fortran package manager has a plugin system that allows it to easily extend its functionality. The fpm-search project is a plugin to query the package registry. Since it is built with fpm we can easily install it on our system.

fpm is a tool that lets you easily create packages for Debian, Ubuntu, Fedora, CentOS, RHEL, Arch Linux, FreeBSD, macOS, and more! fpm isn’t a new packaging system, it’s a tool to help you make packages for existing systems with less effort. It does this by offering a command-line interface to allow you to create packages easily. FPM is written in ruby and can be installed using gem. For some package formats (like rpm and snap), you will need certain packages installed to build them. Some package formats require other tools to be installed on your machine to be built; especially if you are building a package for another operating system/distribution. FPM takes your program and builds packages that can be installed easily on various operating systems. It can take any nodejs package, ruby gem, or even a python package and turn it into a deb, rpm, pacman, etc. package.

Cargo is the Rust package manager. Cargo downloads your Rust package's dependencies, compiles your packages, makes distributable packages, and uploads them to crates.io, the Rust community’s package registry. You can contribute to this book on GitHub. To get started with Cargo, install Cargo (and Rust) and set up your first crate. The commands will let you interact with Cargo using its command-line interface. A Rust crate is either a library or an executable program, referred to as either a library crate or a binary crate, respectively. Loosely, the term crate may refer to either the source code of the target or to the compiled artifact that the target produces. It may also refer to a compressed package fetched from a registry. Your crates can depend on other libraries from crates.io or other registries, git repositories, or subdirectories on your local file system. You can also temporarily override the location of a dependency.

A blazingly fast and futuristic package manager for windows. Unlike any other package manager, Novus uses multithreaded downloads making the download speeds 8 times faster. Apart from being extremely fast, Novus also installs and uninstalls packages concurrently, making it as efficient as possible. Not only are all of Novus’s packages are monitored regularly, but all of them are always up to date and trusted by the community. Apart from being extremely fast, Novus also installs and uninstalls packages concurrently, making it as efficient as possible. Not only are all of Novus’s packages are monitored regularly, but all of them are always up to date and trusted by the community.

Apache Ivy™ is a popular dependency manager focusing on flexibility and simplicity. Find out more about its unique enterprise features, what people say about it, and how it can improve your build system! Ivy is a tool for managing (recording, tracking, resolving, and reporting) project dependencies. Ivy is essentially process agnostic and is not tied to any methodology or structure. Instead, it provides the necessary flexibility and reconfigurability to be adapted to a broad range of dependency management and build processes. While available as a standalone tool, Ivy works particularly well with Apache Ant providing a number of powerful Ant tasks ranging from dependency resolution to dependency reporting and publication. Ivy has a lot of powerful features, the most popular and useful being its flexibility, integration with Ant, and strong transitive dependencies management engine. Ivy is open source and released under a very permissive Apache License.

Introducing AnyTree — the first software deployment system secured by the blockchain. On AnyTree, whatever apps developers distribute or use, are delivered exactly as they are supposed to be. The Software Supply Chain is a high-impact area. Yet there exists a distinctive lack of secure, trustless, verifiable, and transparent delivery of source code/binaries to developers and users in all software fields. Storing your code on a git means it has an owner, a single point of control, which leads to security vulnerabilities. Currently, there is no industrial solution available that is not centralized and thus not dependent on the decisions of a few actors. The main way in which GOSH solves this issue is by allowing developers to build consensus around their code, so the more code is written, the more secure it becomes.

Store and share artifacts across accounts, with appropriate levels of access granted to your teams and build systems. Reduce overhead from setup and maintenance of an artifact server or infrastructure with a fully managed service. Only pay for software packages stored, number of requests made, and data transferred out of Region with pay-as-you-go pricing. Configure CodeArtifact to fetch from public repositories such as the npm Registry, Maven Central, Python Package Index (PyPI), and NuGet. Securely share private packages across organizations by publishing them to a central organizational repository. Build automated approval workflows with CodeArtifact APIs and Amazon EventBridge, with visibility into your packages using AWS CloudTrail. Pull dependencies from CodeArtifact in AWS CodeBuild and publish new versions of your private packages secured with AWS Identity and Access Management (IAM).

PyPI is the official repository for Python software packages, hosting hundreds of thousands of projects that developers can publish and users can discover and install. It supports both source distributions (“sdists”) and pre-built binary “wheels”, allowing packages to include native extensions for different platforms. Projects on PyPI consist of multiple releases, each of which can include various files for different operating systems or Python versions. Metadata for each package includes things like version number, dependencies, licensing, classifiers, description (including rendering Markdown or reStructuredText), and other information that tools like pip use to resolve, download, and install the correct package. PyPI provides search and filtering based on package metadata, letting users find what they need via keywords, compatibility, or other package attributes.

Flox is a development environment manager and package tool that lets developers define, share, and replicate consistent environments across machines by leveraging the Nix ecosystem. Flox lets you create environments via a simple manifest.toml, layering and replacing dependencies precisely where needed. It activates subshells with reproducible dependencies and integrates shell hooks, version constraints, and services (e.g., local databases) to automate setup. Because it runs on the host system (rather than inside containers), developers maintain access to files, configurations, SSH keys, and shell aliases without Docker-style bind mounts. Flox supports cross-platform and multi-architecture environments by default, allowing environments to run identically on various systems; you can constrain them to specific systems or use package groups to manage architecture-specific dependencies.

DPKG is a tool to install, build, remove and manage Debian packages. The primary and more user-friendly front-end for DPKG is aptitude. DPKG itself is controlled entirely via command line parameters, which consist of exactly one action and zero or more options. The action parameter tells DPKG what to do and options control the behavior of the action in some way. DPKG can also be used as a front-end to DPKG-deb(1) and DPKG-query. The list of supported actions can be found later on in the actions section. If any such action is encountered DPKG just runs DPKG-deb or DPKG-query with the parameters given to it, but no specific options are currently passed to them, to use any such option the back-ends need to be called directly. DPKG maintains some usable information about available packages. The information is divided into three classes, states, selection states, and flags. These values are intended to be changed mainly with dselect.

Package, dependency, and environment management for any language, Python, R, Ruby, Lua, Scala, Java, JavaScript, C/ C++, Fortran, and more. Conda is an open-source package management system and environment management system that runs on Windows, macOS, Linux, and z/OS. Conda quickly installs, runs, and updates packages and their dependencies. Conda easily creates, saves, loads, and switches between environments on your local computer. It was created for Python programs, but it can package and distribute software for any language. Conda as a package manager helps you find and install packages. If you need a package that requires a different version of Python, you do not need to switch to a different environment manager, because conda is also an environment manager. With just a few commands, you can set up a totally separate environment to run that different version of Python, while continuing to run your usual version of Python in your normal environment.

just-install is a humble package installer for Windows. just-install provides you the opportunity to install packages, install a specific architecture, check the list of packages, and get help all with simple cms commands.

DNF is a software package manager that installs, updates, and removes packages on Fedora and is the successor to YUM (Yellow-Dog Updater Modified). DNF makes it easy to maintain packages by automatically checking for dependencies and determining the actions required to install packages. This method eliminates the need to manually install or update the package, and its dependencies, using the rpm command. DNF is now the default software package management tool in Fedora. Removes packages installed as dependencies that are no longer required by currently installed programs. Checks for updates, but does not download or install the packages. Provides basic information about the package including name, version, release, and description.

Artifact Registry is Google Cloud’s unified, fully managed package and container registry designed for high-performance artifact storage and dependency management. It centralizes host­ing of container images (Docker/OCI), Helm charts, language packages (Java/Maven, Node.js/npm, Python), and OS packages, offering fast, scalable, reliable, and secure handling with built-in vulnerability scanning and IAM-based access control. Integrated seamlessly with Google Cloud CI/CD tools like Cloud Build, Cloud Run, GKE, Compute Engine, and App Engine, it supports regional and virtual repositories with granular security via VPC Service Controls and customer-managed encryption keys. Developers benefit from standardized Docker Registry API support, comprehensive REST/RPC interfaces, and migration paths from Container Registry. Daily updated documentation includes quickstarts, repository management, access configuration, observability tools, and deep-dive guides.

Master Packager is an application packaging tool to create and edit Microsoft Windows Installer (MSI) files and repackage other installations to MSI format. Our vision is to make application packaging easy, fast, and affordable for everyone, from application packaging freelancers to small companies and enterprises. * Fast - You will never see "not responding" text in the tool. Modifying large MSIs is effortless. The same goes for repackaging. * High quality - Standardized naming, ICE validation, and .dll/.exe file registration mapping are just a few examples of how this tool will reduce human errors and increases quality. * Simple - The user interface allows new and experienced packagers to start creating packages immediately. * Automation - Capturing, building, and applying templates can be fully automated, making it possible to fully automate repackaging. * Price - Providing the same value or better Master Packager can save you money as it can be up to 10 times.

Introducing tea - the revolutionary, cross-platform package manager. Say goodbye to slow & clunky, and say hello to fast & smooth. From the creator of Brew. With tea, simply type commands and it takes care of the rest. Get the latest versions of open source tools and support specific tool versions for different projects. Experience better package management with tea. And through that packaging infrastructure, we have plans of leveraging blockchain to help remunerate devs for their contributions to OSS. You can learn more about our grand ambitions for web3 by checking out our white paper here. Easily access the entire open source ecosystem with tea. Simply prefix your commands with "tea" and if the tool isn't installed, tea will install it for you. Add magic to your shell scripts and use developer environments to enhance your workflow. magic is optional; if you don’t enable it, then just prefix your commands with `tea`.

Bun is a fast, all-in-one JavaScript, TypeScript, and JSX toolkit that ships as a single executable and combines a high-performance runtime, package manager, test runner, and bundler designed as a drop-in replacement for Node.js with broad compatibility and dramatically reduced startup times and memory usage. Written in Zig and powered by Apple’s JavaScriptCore, Bun can execute JavaScript/TypeScript files, scripts, and packages with significantly faster performance than traditional tooling while supporting zero-config TypeScript, JSX, and React out of the box. Its built-in package manager installs dependencies up to 30× faster than npm with workspaces, global caching, migration support, and dependency auditing. Bun’s test runner is Jest-compatible with built-in coverage and concurrent execution, and the bundler processes TypeScript, JSX, CSS, and more without configuration, including support for single-file executables.xx