Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#54941 - Dynamic Dependency

Attached to Project: Pacman
Opened by Utsob Roy (uroybd) - Thursday, 27 July 2017, 02:20 GMT
Last edited by Allan McRae (Allan) - Thursday, 27 July 2017, 02:34 GMT
Task Type Feature Request
Category General
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 5.0.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Every now on then you may find yourself in a situation where your python/ruby packages installed with pip/gem comes into the path of the Pacman's installation or upgradation.

Can we add a checking for this? For example, Let's say you have 'pychromecast' installed via pip.
Now you are installing 'mkchromecast' which have 'python-pychromecast' as dependency which is the package we already have installed via pip. If we have to install mkchromecast now, we have to use '--force' flag now.

My proposal is:
1. Whenever any package have a name starting with 'python-', 'python2-', 'ruby-', it will first check in pip for py3 or py2 or with gem if that package is installed with proper version.
2. If proper version is installed, skip installing that, if installed but not the proper version, force install it. if not installed at all, install.
This task depends upon

Closed by  Allan McRae (Allan)
Thursday, 27 July 2017, 02:34 GMT
Reason for closing:  Won't implement
Comment by Allan McRae (Allan) - Thursday, 27 July 2017, 02:34 GMT
pacman will not take over files it does not know about or interact with other package management systems. This sounds like a disaster waiting to happen.
Comment by Eli Schwartz (eschwartz) - Thursday, 27 July 2017, 02:38 GMT
The job of a package manager is to manage packages in absolute preference and superiority over things like pip/gem.

Do not use pip as root, use `pip --user` or a virtualenv.

pacman will not add complex, ill-defined logic to *abdicate its purpose for existing* in programming-language-specific cases. Especially because pacman cannot guarantee the integrity of your random pip-installed module, it cannot cleanly uninstall, it cannot make sure all dependencies are available *and will continue to be available*, it cannot sanely migrate your pip module when we upgrade to python 3.7, etc...

tl;dr
Stop installing untracked files into / and your problems will go away.

Loading...