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#26990 - [pacman] Integrate with other package managers

Attached to Project: Pacman
Opened by darkraven (darkraven) - Friday, 18 November 2011, 06:30 GMT
Last edited by Allan McRae (Allan) - Sunday, 22 April 2012, 10:29 GMT
Task Type Feature Request
Category General
Status Closed
Assigned To No-one
Architecture All
Severity Very Low
Priority Low
Reported Version 3.5.4
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Nowadays many scripting languages have their own package managers, link CPAN, CRAN, NPM and so on.

If I think install packages using those PMs, pacman won't be aware of packages installed, and thus can't manager them.

It's possible to convert those packages to PKGBUILDs though, with some converter from AUR. But that's quite inconvenient. And installing them locally (not system-wise) is not always a suitable solution.

So I think it'll be good to integrate pacman with other package managers. Pacman should be able to read other PMs' database to get lists of installed packages, and invoke appropriate PM when installing packages from outside of pacman's repo.
This task depends upon

Closed by  Allan McRae (Allan)
Sunday, 22 April 2012, 10:29 GMT
Reason for closing:  Won't implement
Comment by Karol Błażewicz (karol) - Friday, 18 November 2011, 14:16 GMT
bauerbill offered CPAN and Hackage support: http://xyne.archlinux.ca/old_projects/bauerbill/
Comment by darkraven (darkraven) - Friday, 18 November 2011, 14:39 GMT
Did bauerbill handle the package information on CPAN/Hackage's side correctly? I mean, if I install a package using bauerbill, will CPAN/Hackage/etc. aware of the package installed?

Anyway, now I understand that the solution should be a wrapper for pacman, rather than modifying pacman. That kind of wrapper should be able to sync package information between different PMs.
Comment by Allan McRae (Allan) - Sunday, 22 April 2012, 10:29 GMT
Agreed. This is not a job for pacman.

Loading...