Answer by HaoZeke for Non-Root Package Managers
I'd suggest http://linuxbrew.sh/ It's basically a fork of brew for macOS and has precompiled binaries for usage... Especially great for handling older gcc versions. If you really want to install by...
View ArticleAnswer by cristi for Non-Root Package Managers
Yum needs to write to the database, which is own by root. Because of this you can't use it as a normal user. You could try to decompress rpm files (rpm2cpio package.rpm | cpio -idmv) inside a directory...
View ArticleAnswer by eMPee584 for Non-Root Package Managers
There's a new kid on the block: "JuNest (Jailed User NEST) - The Arch Linux based distro that runs upon any Linux distro without root access." @ https://github.com/fsquillace/junest Advantage is that...
View ArticleAnswer by user967489 for Non-Root Package Managers
I use JuJu which basically allows to have a really tiny linux distribution (containing just the package manager) inside your $HOME/.juju directory. It allows to have your custom system inside the home...
View ArticleAnswer by Michael Ekstrand for Non-Root Package Managers
If you're fine with compiling from source and resolving dependencies yourself, primarily wanting the package manager to handle deploy/undeploy/upgrade operations, you might want to take a look at GNU...
View ArticleAnswer by Michael Ekstrand for Non-Root Package Managers
Another one with a rather different model is 0install. It's based on the idea that you don't really install packages, but merely run them from a global namespace which downloads, compiles if necessary,...
View ArticleAnswer by new123456 for Non-Root Package Managers
The tools used by Slackware, specifically installpkg, can. From the man page: --root /otherroot Install using a location other than / (the default) as the root of the filesystem to install on. In the...
View ArticleAnswer by imz -- Ivan Zakharyaschev for Non-Root Package Managers
There's a package manager project--Nix--with an interesting foundational idea (a "functional" pkg manager), which also supports a per-user operation: Multi-user support Starting at version 0.11, Nix...
View ArticleAnswer by James Antill for Non-Root Package Managers
My experience is really just limited to yum, but I don't understand why I wouldn't be able to drop a repo file into ~/etc/yum.repos.d and have yum install everything into a home account. The...
View ArticleAnswer by ephemient for Non-Root Package Managers
Binary packages are compiled with the assumption that they will be installed to specific locations in /. This is not always easily changed, and it would take additional QA effort (which is difficult...
View ArticleAnswer by Maciej Piechotka for Non-Root Package Managers
First of all it is due to dependencies. Some packages may not be installed by user - like PolicyKit. Therefore it would require additional burden on packager who donate their free time and usually...
View ArticleNon-Root Package Managers
From my research, I seem to notice that all package managers insist on being used as a privileged user and must be installed into /. Typically, what I like to do is create a throwaway account, compile...
View ArticleAnswer by Badr Elmers for Non-Root Package Managers
and a new one is zpkg, it is magic:With zpkg you can install programs from other distributions into your systemzpkg will install programs to your home directory. Global installations are also supported...
View Article
